Unsolvable

[apinto]

Hi there,

First, I would like to say that I've read the FAQ, the READ THIS FIRST and searched for posts regarding this issue. But, although it's a common question, nothing seams to solve my problem.

I have an application (EAR) that creates a JMS topic, that has two durable subscriptors and one non-durable, all loaded in the same JBoss instance. After some time running, or after periods of higher load, the JMS subsystem starts throwing "ping timeout" messages, similar to the following:


2004-08-06 07:49:28,284 WARN [org.jboss.mq.Connection] Connection failure:
org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection.asynchFailure(Connection.java:718)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1311)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1303)
... 2 more


What can I do, in terms of debug or configuration, to find and solve the problem? Thanks in advance,

Armenio Pinto

[genman]

JBoss version? Are you using java:/JmsXA as your client factory?

[apinto]

"genman" wrote:

JBoss version? Are you using java:/JmsXA as your client factory?

Sorry for the lack of information. In JBoss 3.2.3 we don't have this problem... It only happens in JBoss 3.0.7, that we must support for business reasons. Regarding the client factory, we only use ConnectionFactory. Thanks,

Arménio Pinto

[genman]

For supporting older versions, I would suggest a support contract.

Otherwise, you can shut the warning up using log4j configuration. Submitting a test case would be helpful. The ping timeout occurs when the server thinks a client has disconnected. It could be that the later version of JBoss is more lax with clients.