Hi,
Lately we experience more of these JMS ping timeouts in one of our
"almost production" installations. We get these exceptions on the client
side. On the server side we use JBoss 3.0.5 with the UIL IL.
Here is the exception:
-----------------------------------------------------
17:47:39,093 WARN Connection - Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable:
(java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:606)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1190)
at
EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav
a:364)
at java.lang.Thread.run(Unknown Source)
+ nested throwable:
java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1182)
at
EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav
a:364)
at java.lang.Thread.run(Unknown Source)
-----------------------------------------------------
The client still seems to work, except that we see a lot of these
messages in the log output.
What could be a cause of this? Could it be related to a slow network?
And finally will JMS continue to work reliably?
Regards,
Sebastian
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
