Re: jndi exceptions

I'd suggest upgrading to 0.7.7-beta-1. The connection management code had
a number of fixes applied since alpha-3.

-Tim


Michael Masters wrote:
> I've attached a file with the code I've been running. Sometimes the
> code will work without any issues, but it seems to randomly have the
> exception I mentioned earlier. The version I'm using is OpenJMS
> 0.7.7-alpha-3.
>
> Thanks,
> Mike
>
> On 4/9/07, Tim Anderson <[email protected]> wrote:
>> It means that the connection to the server has been unexpectedly lost.
>> Can you send a minimal test case which reproduces the problem,
>> and indicate which version you are running?
>>
>> Thanks,
>>
>> -Tim
>>
>> Michael Masters wrote:
>> > I have a little test program where I have a sender thread and several
>> > listener threads. I seem to randomly get the following exception:
>> >
>> > javax.naming.ServiceUnavailableException: Connection lost [Root
>> > exception is org.exolab.jms.net.connector.ResourceException:
>> > Connection lost]
>> >       at 
>> org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFactory.java:177) 
>>
>> >       at 
>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
>> >       at 
>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
>> >       at javax.naming.InitialContext.init(InitialContext.java:219)
>> >       at javax.naming.InitialContext.<init>(InitialContext.java:175)
>> >       at com.ibm.ptest.jms.Listener.run(Listener.java:49)
>> > Caused by: org.exolab.jms.net.connector.ResourceException: 
>> Connection lost
>> >       at 
>> org.exolab.jms.net.multiplexer.MultiplexedManagedConnection.invoke(MultiplexedManagedConnection.java:354) 
>>
>> >       at 
>> org.exolab.jms.net.multiplexer.MultiplexedConnection.invoke(MultiplexedConnection.java:86) 
>>
>> >       at 
>> org.exolab.jms.net.connector.ManagedConnectionHandle$ConnectionHandle.invoke(ManagedConnectionHandle.java:263) 
>>
>> >       at 
>> org.exolab.jms.net.orb.UnicastDelegate.invoke(UnicastDelegate.java:153)
>> >       at org.exolab.jms.net.proxy.Proxy.invoke(Proxy.java:102)
>> >       at 
>> org.exolab.jms.server.net.RemoteNamingProvider__Proxy.getNameParser(RemoteNamingProvider__Proxy.java:71) 
>>
>> >       at 
>> org.exolab.jms.jndi.InitialContextFactory.getInitialContext(InitialContextFactory.java:173) 
>>
>> >       ... 5 more
>> >
>> >
>> > Could someone explain to me what this means or how I can resolve it? I
>> > assume one thread is unable to get the initial context while another
>> > thread has a hold of it. Is this true?
>> >
>> > Thanks in advance,
>> > Michael Masters
>> >

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV