"Unable to send ping" message on JBossEAP client side
Issue
- We have recently started getting the following error in our logs, so far just on local workstations and not on a server cluster. The error continues to be logged, about once every 10 seconds.
Can you please explain what this error means, and how to eliminate it?
WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] - 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(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:115)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
or
WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-7) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
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:735)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Environment
- Red JBoss Hat Enterprise Application Platform (EAP)
- 4.3
- 5.x
- JBoss Messaging
- 1.4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
