JBoss Community

PingTimerTask in JBoss AS 5.0.1.GA EAP

created by Kevin Lohmann in JBoss Remoting - View the full discussion

Hi there,

 

since we switched to JBoss 5.0.1.GA EAP (from 5.1.0.GA), plenty of times we see warnings in server.log like this:

 

2010-08-31 16:34:37,211 WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Connection reset by peer: socket write error
 at java.net.SocketOutputStream.socketWrite0(Native Method)
 at java.net.SocketOutputStream.socketWrite(Unknown Source)
 at java.net.SocketOutputStream.write(Unknown Source)
 at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
 at java.util.TimerThread.mainLoop(Unknown Source)
 at java.util.TimerThread.run(Unknown Source)

 

Or:

 

2010-08-31 22:18:38,519 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Socket closed
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)

 

Or:

 

2010-08-31 15:06:24,248 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Software caused connection abort: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)

 

Or:

 

2010-08-31 18:38:11,886 WARN  [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.lang.NullPointerException
    at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)


 

 

I can imagine what the PingTimerTask should do. But I'd like to hear from the experts what they say about it.

 

How can we handle these warnings?

 

Sometimes our clients receive warnings like this:

 

WARNING org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@1f175da: detected failure on control connection Thread[control: Socket[addr=XXX/yyyy,port=7063,localport=4328],3,main] (a2sc3v-fo68je-gdiugvr5-1-gdjopipw-llpl: requesting new control connection (org.jboss.remoting.transport.bisocket.BisocketServerInvoker)

 

which we consider to be a part of the warnings the server logs. Can that be? Or is it another phenomenon?

 

I can't find any informations about these questions. The ones I see are out of date (three years ago)...

 

Anyone who can help me?

 

Thanks in advance,

Kevin

Reply to this message by going to Community

Start a new discussion in JBoss Remoting at Community