[jboss-user] [Messaging, JMS & JBossMQ] - Weird behavior with ping timeouts

Friday, 15 September 2006

Hello all,

I was wondering if anyone has seen the following behavior before, and if anyone knows a
solution for it. We appear to have messages that aren't being delivered. The following
is a snip of our logs:

  | 2006-09-15 11:27:59,543 WARN  [org.jboss.mq.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:1277)
  | 	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
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.SocketManager] Read msgType:
m_ping, msgID: 64
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.SocketManager] Read new msg:
org.jboss.mq.il.uil2.msgs.PingMsg1890854[msgType: m_ping, msgID: 64, error: null]
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Begin
handleMsg, msgType: 21
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : ping
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.server.TracingInterceptor] ARG    :
1158334085647
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.SocketManager] Begin
internalSendMessage, one-way msg=org.jboss.mq.il.uil2.msgs.PingMsg9602832[msgType: m_pong,
msgID: -2147466927, error: null]
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.SocketManager] Write msg:
org.jboss.mq.il.uil2.msgs.PingMsg9602832[msgType: m_pong, msgID: -2147466927, error:
null]
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.SocketManager] End
internalSendMessage, msg=org.jboss.mq.il.uil2.msgs.PingMsg9602832[msgType: m_pong, msgID:
-2147466927, error: null]
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : ping
  | 2006-09-15 11:28:06,308 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] End
handleMsg, msgType: 21
  | 2006-09-15 11:28:11,121 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Begin
handleMsg, msgType: 21
  | 2006-09-15 11:28:11,121 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : ping
  | 2006-09-15 11:28:11,121 TRACE [org.jboss.mq.server.TracingInterceptor] ARG    :
1158334092214
  | 2006-09-15 11:28:11,121 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : ping
  | 2006-09-15 11:28:11,121 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] End
handleMsg, msgType: 21
  | ... traced ping message repeats ...
  | 2006-09-15 11:28:46,120 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Begin
handleMsg, msgType: 21
  | 2006-09-15 11:28:46,120 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : ping
  | 2006-09-15 11:28:46,120 TRACE [org.jboss.mq.server.TracingInterceptor] ARG    :
1158334126064
  | 2006-09-15 11:28:46,120 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : ping
  | 2006-09-15 11:28:46,120 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] End
handleMsg, msgType: 21
  | 2006-09-15 11:28:59,557 WARN  [org.jboss.mq.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:1277)
  | 	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
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.SocketManager] Read msgType:
m_ping, msgID: 65
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.SocketManager] Read new msg:
org.jboss.mq.il.uil2.msgs.PingMsg18189100[msgType: m_ping, msgID: 65, error: null]
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Begin
handleMsg, msgType: 21
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : ping
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.server.TracingInterceptor] ARG    :
1158334145653
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.SocketManager] Begin
internalSendMessage, one-way msg=org.jboss.mq.il.uil2.msgs.PingMsg8764440[msgType: m_pong,
msgID: -2147466921, error: null]
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.SocketManager] Write msg:
org.jboss.mq.il.uil2.msgs.PingMsg8764440[msgType: m_pong, msgID: -2147466921, error:
null]
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.SocketManager] End
internalSendMessage, msg=org.jboss.mq.il.uil2.msgs.PingMsg8764440[msgType: m_pong, msgID:
-2147466921, error: null]
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : ping
  | 2006-09-15 11:29:06,323 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] End
handleMsg, msgType: 21
  | 2006-09-15 11:29:11,135 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Begin
handleMsg, msgType: 21
  | 2006-09-15 11:29:11,135 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : ping
  | 2006-09-15 11:29:11,135 TRACE [org.jboss.mq.server.TracingInterceptor] ARG    :
1158334152238
  | 2006-09-15 11:29:11,135 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : ping
  | 2006-09-15 11:29:11,135 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] End
handleMsg, msgType: 21
  | .. more ping messages...
  | 

We have 3 different database connections open, in addition to the JMS backend which is
still the default Hypersonic one. It appears some of the logged pings are for those.
I'm tracing with the following (from READTHISFIRST) but I'm not sure what other
diagnostic information to aquire.
<category name="org.jboss.mq">
  |      <priority value="TRACE"
class="org.jboss.logging.XLevel"/>
  | </category>

My uil2-service.xml contains     
  |     <attribute name="PingPeriod">60000</attribute>, so I
shouldn't really be having this big of a problem with ping timeouts. After all, the
JMS backend is a local database on the same machine, with mostly the default JBoss
installer-configured settings.

Can anyone suggest the problem or even other ways to analyze it? Thank you.

View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971956#...

Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[jboss-user] [Messaging, JMS & JBossMQ] - Weird behavior with ping timeouts