[jboss-user] [JBoss Messaging] - Re: PingTimerTask broken pipe

bob_walker99 do-not-reply at jboss.com
Mon Sep 10 06:42:21 EDT 2007


I'm still seeing this after the upgrade to 1.4.0-CR2:

2007-09-10 11:26:03,237 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask
  |  java.net.SocketException: Write failed: Broken pipe
  |      at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
  |      at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:45)
  |      at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java)
  |      at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
  |      at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
  |      at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:612)
  |      at java.util.TimerThread.mainLoop(Timer.java:512)
  |      at java.util.TimerThread.run(Timer.java:462)
  | 2007-09-10 11:26:03,308 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,327 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,327 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,327 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: trying again
  | 2007-09-10 11:26:03,370 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] Unable to send ping: shutting down PingTimerTask
  |  java.net.SocketException: Write failed: Broken pipe
  |      at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
  |      at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:45)
  |      at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java)
  |      at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
  |      at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
  |      at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:612)
  |      at java.util.TimerThread.mainLoop(Timer.java:512)
  |      at java.util.TimerThread.run(Timer.java:462)
  | 2007-09-10 11:26:06,064 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[14071c5, bisocket://10.0.2.15:1698313622] replacing control socket: Socket[addr=/10.0.2.15,port=24004,localport=3692]
  | 2007-09-10 11:26:06,064 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[14071c5, bisocket://10.0.2.15:1698313622] control socket replaced by: Socket[addr=/10.0.2.15,port=24109,localport=3692]
  | 2007-09-10 11:26:06,334 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[14e5a8d, bisocket://10.0.2.15:1699615737] replacing control socket: Socket[addr=/10.0.2.15,port=24003,localport=3692]
  | 2007-09-10 11:26:06,420 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[14e5a8d, bisocket://10.0.2.15:1699615737] control socket replaced by: Socket[addr=/10.0.2.15,port=24111,localport=3692]
  | 2007-09-10 11:26:06,457 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[1409e1c, bisocket://10.0.2.15:1699584984] replacing control socket: Socket[addr=/10.0.2.15,port=24034,localport=3692]
  | 2007-09-10 11:26:06,522 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] SocketClientInvoker[1409e1c, bisocket://10.0.2.15:1699584984] control socket replaced by: Socket[addr=/10.0.2.15,port=24110,localport=3692]
  | 

Do I need to worry about this? It looks like perhaps is it just indicating that the Bisocket control is working, detecting a connection error, and re-initiliasing itself with that client, but I want to make sure everything is as it should be?

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

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



More information about the jboss-user mailing list