Re: JNDI service is not bound in the registry for URL

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 <[email protected]> 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="192.168.51.10" embeddedJNDI="true" />
> 
>   <RmiConfiguration embeddedRegistry="true"
>                     registryHost="192.168.51.10"
>                     registryPort="1099">
>   </RmiConfiguration>
> 
> > -----Original Message-----
> > From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> > [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> > Of Contremo
> > Sent: Tuesday, 31 May 2005 8:40 PM
> > To: [email protected]
> > Subject: [openjms-user] JNDI service is not bound in the 
> > registry for URL
> > 
> > 
> > Hi all
> > 
> > First, I apologize my poor english.
> > 
> > I have a little problem running the OpenJMS 0.7.6.1. When 
> > launch the service and inmediately the runsender example, I 
> > got the next error:
> > 
> >  javax.naming.ServiceUnavailabl
> > eException: JNDI service is not bound in the
> >  registry for URL: rmi://192.168.51.10:1099/JndiServer
> >         at 
> > org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory.getInitia
> > lContext(RmiJndiI
> > nitialContextFactory.java:140)
> >         at 
> > org.exolab.jms.jndi.InitialContextFactory.getInitialContext(In
> > itialContextFacto
> > ry.java:109)
> >         at 
> > javax.naming.spi.NamingManager.getInitialContext(NamingManager
> > .java:667)
> >         at 
> > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> >         at javax.naming.InitialContext.init(InitialContext.java:223)
> >         at javax.naming.InitialContext.<init>(InitialContext.java:197)
> >         at 
> > openjms.examples.client.console.ContextHelper.getContext(Conte
> > xtHelper.java:121
> > )
> >         at 
> > openjms.examples.client.console.SimpleSender.main(SimpleSender
> > .java:95)
> > 
> > where 192.168.51.10 is the IP address of my computer. This is 
> > defined changing the openjms.xml line:
> > 
> > <ServerConfiguration host="localhost" embeddedJNDI="true" />
> > 
> > This change was made because before OpenJMS assumed 
> > 192.168.1.1 as the localhost  IP. I have probed to set 
> > embedded JNDI="false" and configure JNDI as a external 
> > provider, but no solution here.
> > 
> > This is not all, folks!
> > 
> > If I launch runsender a few minutes later, he tryes to 
> > connect to the service, and many minutes later I have a 
> > beautiful timeout like this:
> > 
> > javax.naming.ServiceUnavailableException: Connection refused 
> > to host: 192.168.1.1; nested exception is:
> >         java.net.ConnectException: Connection timed out [Root 
> > exception is java.rmi.ConnectException: Connection refused to 
> > host: 192.168.1.1; nested exception is:
> >         java.net.ConnectException: Connection timed out]
> >         at 
> > org.exolab.jms.jndi.rmi.RmiJndiInitialContextFactory.getInitia
> > lContext(RmiJndiInitialContextFactory.java:155)
> >         at 
> > org.exolab.jms.jndi.InitialContextFactory.getInitialContext(In
> itialContextFactory.java:109)
> >         at 
> > javax.naming.spi.NamingManager.getInitialContext(NamingManager
> > .java:667)
> >         at 
> > javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
> >         at javax.naming.InitialContext.init(InitialContext.java:223)
> >         at javax.naming.InitialContext.<init>(InitialContext.java:197)
> >         at 
> > openjms.examples.client.console.ContextHelper.getContext(Conte
> > xtHelper.java:121)
> >         at 
> > openjms.examples.client.console.SimpleSender.main(SimpleSender
> > .java:95)
> > Caused by: java.rmi.ConnectException: Connection refused to 
> > host: 192.168.1.1; nested exception is:
> >         java.net.ConnectException: Connection timed out
> >         at 
> > sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
> >         at 
> > sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
> >         at 
> > sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
> >         at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
> >         at 
> > org.apache.avalon.excalibur.naming.rmi.server.RMINamingProvide
> > rImpl_Stub.getNameParser(Unknown
> > Source)
> >         at 
> > 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 
> > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> >         at 
> > 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 
> > sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RM
> IDirectSocketFactory.java:22)
> >         at 
> > sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RM
> IMasterSocketFactory.java:128)
> >         at 
> > sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
> >         ... 12 more
> > 
> > I don't know why try to connect 192.168.1.1 if this address 
> > is not set in my configuration files or java code.
> > 
> > I don't know why last friday this example works, but 
> > yesterdey (and today) not.
> > 
> > Have I a gremlin or simply a headache?
> > 
> > Thanks all coming help
> > 
> > 
> > -------------------------------------------------------
> > 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=fad-ysdn-ostg-q22005
> > _______________________________________________
> > openjms-user mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openjms-user
> > 
> 
> 
> 
> -------------------------------------------------------
> 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=offad-ysdn-ostg-q22005
> _______________________________________________
> openjms-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openjms-user
> 

-- 
Sergio Valije Guiadanes


-------------------------------------------------------
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=offad-ysdn-ostg-q22005