From: Contremo <con...@gm...> - 2005-06-01 07:34:48
|
The problem still remains and I have the same errors. I configured my laptop with the old configuration params and all works properly... but not in the PC. I have suffered a blackout last week end. Before OpenJMS works, but after not and the related problem has appeared. Regards On 5/31/05, Tim Anderson <tm...@ne...> wrote: > Wherever "localhost" appears in openjms.xml, the > server changes it to the IP address of the local host. > You probably need the following: > <ServerConfiguration host=3D"192.168.51.10" embeddedJNDI=3D"true" /> >=20 > <RmiConfiguration embeddedRegistry=3D"true" > registryHost=3D"192.168.51.10" > registryPort=3D"1099"> > </RmiConfiguration> >=20 > > -----Original Message----- > > From: ope...@li...=20 > > [mailto:ope...@li...] On Behalf=20 > > Of Contremo > > Sent: Tuesday, 31 May 2005 8:40 PM > > To: ope...@li... > > Subject: [openjms-user] JNDI service is not bound in the=20 > > registry for URL > >=20 > >=20 > > Hi all > >=20 > > First, I apologize my poor english. > >=20 > > I have a little problem running the OpenJMS 0.7.6.1. When=20 > > launch the service and inmediately the runsender example, I=20 > > got the next error: > >=20 > > javax.naming.ServiceUnavailabl > > eException: JNDI service is not bound in the > > registry for URL: rmi://192.168.51.10:1099/JndiServer > > at=20 > > org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory.getInitia > > lContext(RmiJndiI > > nitialContextFactory.java:140) > > at=20 > > org.exolab.jms.jndi.InitialContextFactory.getInitialContext(In > > itialContextFacto > > ry.java:109) > > at=20 > > javax.naming.spi.NamingManager.getInitialContext(NamingManager > > .java:667) > > at=20 > > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) > > at javax.naming.InitialContext.init(InitialContext.java:223) > > at javax.naming.InitialContext.<init>(InitialContext.java:197) > > at=20 > > openjms.examples.client.console.ContextHelper.getContext(Conte > > xtHelper.java:121 > > ) > > at=20 > > openjms.examples.client.console.SimpleSender.main(SimpleSender > > .java:95) > >=20 > > where 192.168.51.10 is the IP address of my computer. This is=20 > > defined changing the openjms.xml line: > >=20 > > <ServerConfiguration host=3D"localhost" embeddedJNDI=3D"true" /> > >=20 > > This change was made because before OpenJMS assumed=20 > > 192.168.1.1 as the localhost IP. I have probed to set=20 > > embedded JNDI=3D"false" and configure JNDI as a external=20 > > provider, but no solution here. > >=20 > > This is not all, folks! > >=20 > > If I launch runsender a few minutes later, he tryes to=20 > > connect to the service, and many minutes later I have a=20 > > beautiful timeout like this: > >=20 > > javax.naming.ServiceUnavailableException: Connection refused=20 > > to host: 192.168.1.1; nested exception is: > > java.net.ConnectException: Connection timed out [Root=20 > > exception is java.rmi.ConnectException: Connection refused to=20 > > host: 192.168.1.1; nested exception is: > > java.net.ConnectException: Connection timed out] > > at=20 > > org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory.getInitia > > lContext(RmiJndiInitialContextFactory.java:155) > > at=20 > > org.exolab.jms.jndi.InitialContextFactory.getInitialContext(In > itialContextFactory.java:109) > > at=20 > > javax.naming.spi.NamingManager.getInitialContext(NamingManager > > .java:667) > > at=20 > > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) > > at javax.naming.InitialContext.init(InitialContext.java:223) > > at javax.naming.InitialContext.<init>(InitialContext.java:197) > > at=20 > > openjms.examples.client.console.ContextHelper.getContext(Conte > > xtHelper.java:121) > > at=20 > > openjms.examples.client.console.SimpleSender.main(SimpleSender > > .java:95) > > Caused by: java.rmi.ConnectException: Connection refused to=20 > > host: 192.168.1.1; nested exception is: > > java.net.ConnectException: Connection timed out > > at=20 > > sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574) > > at=20 > > sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185) > > at=20 > > sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171) > > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94) > > at=20 > > org.apache.avalon.excalibur.naming.rmi.server.RMINamingProvide > > rImpl_Stub.getNameParser(Unknown > > Source) > > at=20 > > org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory.getInitia > > lContext(RmiJndiInitialContextFactory.java:151) > > ... 7 more > > Caused by: java.net.ConnectException: Connection timed out > > at java.net.PlainSocketImpl.socketConnect(Native Method) > > at=20 > > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > > at=20 > > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364) > > at java.net.Socket.connect(Socket.java:507) > > at java.net.Socket.connect(Socket.java:457) > > at java.net.Socket.<init>(Socket.java:365) > > at java.net.Socket.<init>(Socket.java:178) > > at=20 > > sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RM > IDirectSocketFactory.java:22) > > at=20 > > sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RM > IMasterSocketFactory.java:128) > > at=20 > > sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569) > > ... 12 more > >=20 > > I don't know why try to connect 192.168.1.1 if this address=20 > > is not set in my configuration files or java code. > >=20 > > I don't know why last friday this example works, but=20 > > yesterdey (and today) not. > >=20 > > Have I a gremlin or simply a headache? > >=20 > > Thanks all coming help > >=20 > >=20 > > ------------------------------------------------------- > > This SF.Net email is sponsored by Yahoo. > > Introducing Yahoo! Search Developer Network - Create apps=20 > > using Yahoo! Search APIs Find out how you can build Yahoo!=20 > > directly into your own Applications - visit=20 > > http://developer.yahoo.net/?fr=3Dfad-ysdn-ostg-q22005 > > _______________________________________________ > > openjms-user mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/openjms-user > >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/?fr=3Doffad-ysdn-ostg-q22= 005 > _______________________________________________ > openjms-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openjms-user >=20 --=20 Sergio Valije Guiadanes |