[jboss-jira] [JBoss JIRA] Commented: (JBAS-1489) MessageListener does not invoke ExceptionListener on error
Sumedh inamdar (JIRA)
jira-events at jboss.com
Wed Aug 9 08:31:12 EDT 2006
[ http://jira.jboss.com/jira/browse/JBAS-1489?page=comments#action_12340911 ]
Sumedh inamdar commented on JBAS-1489:
--------------------------------------
I am getting this problem in 4.0.2 as well. :(
I am using an MDB as a queue listener. I could not yet find out the exact use case of the error.
Stack trace follows...
17:42:37,487 WARN [Connection] Connection failure, use javax.jms.Connection.setExceptionListener() to handle this error and reconnect
org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOException: ping timeout.)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1323)
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.
... 3 more
17:43:37,487 WARN [Connection] Connection failure, use javax.jms.Connection.set
ExceptionListener() to handle this error and reconnect
org.jboss.mq.SpyJMSException: No pong received; - nested throwable: (java.io.IOE
xception: ping timeout.)
at org.jboss.mq.Connection$PingTask.run(Connection.java:1323)
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.
... 3 more
---------------
Thank you,
Sumedh
> MessageListener does not invoke ExceptionListener on error
> ----------------------------------------------------------
>
> Key: JBAS-1489
> URL: http://jira.jboss.com/jira/browse/JBAS-1489
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMS service
> Affects Versions: JBossAS-4.0.1 SP1, JBossAS-3.2.7 Final, JBossAS-4.0.1 Final
> Reporter: Adrian Brock
> Assigned To: Adrian Brock
> Fix For: JBossAS-4.0.2RC1
>
>
> If SpyMessageConsumer detects an error on the MessageListener thread
> it should invoke the ExceptionListener.
> Also, to avoid potential deadlocks with exceptions detected on the MessageListener
> thread, a new thread should be started to invoke the ExceptionListener.
> Otherwise the ExceptionListener will not be able to close the consumer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list