RE: Lost Connection Error

The client is failing to ping the server.

To help diagnose why, configure log4j in your client to log:

  <category
name="org.exolab.jms.net.multiplexer.MultiplexedManagedConnection"
additivity="false">
    <priority value="DEBUG"/>
    <appender-ref ref="STDOUT"/>
    <appender-ref ref="openjms"/>
  </category>

  <category name="org.exolab.jms.net.multiplexer.DefaultConnectionPool"
additivity="false">
    <priority value="DEBUG"/>
    <appender-ref ref="STDOUT"/>
    <appender-ref ref="openjms"/>
  </category>

See http://openjms.sourceforge.net/faq.html#logging-log4j-client for
instructions on configuring log4j in your client.

-Tim
 

> -----Original Message-----
> From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 
> [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf 
> Of Steve Mactaggart
> Sent: Monday, 11 July 2005 2:14 PM
> To: [email protected]
> Subject: [openjms-user] Lost Connection Error
> 
> Hey all,
> 
> Now that I have got 0.7.7-alpha-1 working it seems to work 
> fine, except that I keep getting the following error thrown 
> every 30 seconds or so through the
> onException() method on the queue or topic factories.
> 
> 
> 11 Jul 05 13:16:57:ManagedConnectionReaper1:JMSBroker         
>   :ERROR :
> Lost connection
> javax.jms.JMSException: Lost connection
>         at
> org.exolab.jms.client.net.JmsServerStubImpl.disconnected(JmsSe
> rverStubImpl.j
> ava:195)
>         at
> org.exolab.jms.net.connector.MulticastCallerListener.disconnec
> ted(MulticastC
> allerListener.java:129)
>         at
> org.exolab.jms.net.connector.DefaultConnectionPool.notifyDisco
> nnection(Defau
> ltConnectionPool.java:495)
>         at
> org.exolab.jms.net.connector.DefaultConnectionPool.remove(Defa
> ultConnectionP
> ool.java:476)
>         at
> org.exolab.jms.net.connector.DefaultConnectionPool$Reaper.reap
> DeadConnection
> s(DefaultConnectionPool.java:626)
>         at
> org.exolab.jms.net.connector.DefaultConnectionPool$Reaper.run(
> DefaultConnect
> ionPool.java:546)
>         at 
> EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown
> Source)
>         at java.lang.Thread.run(Thread.java:534)
> 
> 
> I'm not sure if it is a configuration issue on my end, or an 
> issue in the new 0.7.7 release.
> Any ideas or discussion are greatly welcome..
> 
> Thanks,
> 
> Steve
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' 
> webinar happening July 14 at 8am PDT/11am EDT. We invite you 
> to explore the latest in dual core and dual graphics 
> technology at this free one hour event hosted by HP, AMD, and 
> NVIDIA.  To register visit http://www.hp.com/go/dualwebinar 
> _______________________________________________
> openjms-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openjms-user
> 



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar