SpyJMSException without cause

[pvaibhav]

We are experianceing a strange problem about our MDB.

We have a workflow engine with one MDB some session beans and entity beans.

Suddenly a SpyJMSException occurs and it keeps on coming every minute from that moment till you restart the server.

There is no cause mentioned with the stack trace. It only says Connection Failiure. The stack trace is given below.

This has happened on Jboss 3.2.5, 4.0.1 and 4.0.1 sp1.

Looks like for some reason queue gets disconnected.

Can anybody throw light on this?


-----------------------------------------------------------------------------

2005-02-18 20:21:39,991 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:436)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1385)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1377)
... 2 more
2005-02-18 20:22:39,992 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:436)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1385)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1377)
... 2 more
2005-02-18 20:23:39,993 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:436)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1385)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1377)
... 2 more
2005-02-18 20:24:40,000 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:436)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1385)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1377)
... 2 more
2005-02-18 20:25:40,007 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:436)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1385)
at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.java:364)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.io.IOException: ping timeout.
at org.jboss.mq.Connection$PingTask.run(Connection.java:1377)
... 2 more

[adrian.brock]

Moderated: FAQ

[sonntag]

Moderated: FAQ

which one? link?
thx alot! :))

[pvaibhav]

I think I did not clarify some things

1) The same code on Jboss 3.2.3 works fine and does not produce this exception.

2) The exception is generated when nothing is happening. Without any event from our application.

3) Looks like both ends in this are Jboss - the queue and something that keeps on pinging the queue. We understand that sunddenly queue stops listening and the thread that is pinging throws this exception.

But why is queue stopping suddenly? Without our application doing anything.

4) This problem is seen on Windows 2003 Server + Jboss 3.2.5 and
Windows XP + Jboss 4.0.1 and Windows XP + Jboss 4.0.1 sp1.

Does this information make you conclude anything?

[adrian.brock]

It tells me the following:

If you don't have the time/inclination/ability to "READ THIS FIRST" or the FAQ or the documentation or the spec,
I don't have the time/inclination/ability to help you.

I've even changed the warning in JBoss-4.0.2 just to try this forum being
filled up with the same questions over and over again.

log.warn("Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect", excep);

FAQ means the question has been asked too many times,
nobody is interested in answering repeat questions from lazy users.

Moderated: END OF THREAD

[mwaschkowski]

FAQ means the question has been asked too many times,
nobody is interested in answering repeat questions from lazy users.

This isn't helpful.
1) FAQ means "a series of questions and answers."
see: http://en.wikipedia.org/wiki/Faq
it does NOT mean your explanation, which has a condescending tone to it
2) There is simply no need to describe people as lazy. The person may be lazy, or may be uninformed, but you don't know which (which you did indicate in your response) so this just comes across as a personal dig.

Adrian, you've helped so many people (including me), but posts like this just create tension and detract from your helpful reputation. Please, try and keep the negative commentary to yourself.

Regards,

Mark