]
Mark Little updated JBESB-312:
------------------------------
Fix Version/s: 4.2 Milestone Release 2
(was: 4.2)
StandaloneBootStrapper Messages
-------------------------------
Key: JBESB-312
URL:
http://jira.jboss.com/jira/browse/JBESB-312
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.0
Reporter: Burr Sutter
Assigned To: Kevin Conner
Priority: Minor
Fix For: 4.2 Milestone Release 2
When the application server is restarted out from under a live running listener (via the
Standalonebootstrapper) it does appear to work once the app server is brought back to
life. However, it produces a long stacktrace. Even after it redeploys the services (even
though it shouldn't hav redeployed the servcies because their config file was
untouched) it continues to complain and throw up errors/warnings until freshly restarted.
[java] 19:15:14,465 WARN [Connection Monitor Thread][Connection] Connectio
n failure, use javax.jms.Connection.setExceptionListener() to handle this error
and reconnect
[java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(java.io.IOException: ping timeout.)
[java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
[java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Cloc
kDaemon.java:364)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: ping timeout.
[java] ... 3 more
[java] 19:15:18,027 WARN [Connection Monitor Thread][Connection] Connectio
n failure, use javax.jms.Connection.setExceptionListener() to handle this error
and reconnect
[java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(java.io.IOException: ping timeout.)
[java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
[java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Cloc
kDaemon.java:364)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: ping timeout.
[java] ... 3 more
[java] 19:15:18,027 WARN [Connection Monitor Thread][Connection] Connectio
n failure, use javax.jms.Connection.setExceptionListener() to handle this error
and reconnect
[java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(java.io.IOException: ping timeout.)
[java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
[java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Cloc
kDaemon.java:364)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: ping timeout.
[java] ... 3 more
[java] 19:15:18,183 WARN [Connection Monitor Thread][Connection] Connectio
n failure, use javax.jms.Connection.setExceptionListener() to handle this error
and reconnect
[java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(java.io.IOException: ping timeout.)
[java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
[java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Cloc
kDaemon.java:364)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: ping timeout.
[java] ... 3 more
[java] 19:15:18,308 WARN [Connection Monitor Thread][Connection] Connectio
n failure, use javax.jms.Connection.setExceptionListener() to handle this error
and reconnect
[java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(java.io.IOException: ping timeout.)
[java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
[java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Cloc
kDaemon.java:364)
[java] at java.lang.Thread.run(Thread.java:595)
[java] Caused by: java.io.IOException: ping timeout.
[java] ... 3 more
[java] 19:15:20,043 WARN [Connection Monitor Thread][Connection] Connectio
n failure, use javax.jms.Connection.setExceptionListener() to handle this error
and reconnect
[java] org.jboss.mq.SpyJMSException: No pong received; - nested throwable:
(java.io.IOException: ping timeout.)
[java] at org.jboss.mq.Connection$PingTask.run(Connection.java:1277)
[java] at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Cloc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: