[Messaging, JMS & JBossMQ] - Broken Pipe
by guinsu
Since upgrading to JBoss 4.0.5 and Messaging 1.2beta I've gotten a broken pipe error twice while running under high load for extended periods. If I stop and restart the one Queue that is being affected, as well as restart all the clients of that queue, things start working again. This is similar to the behavior I used to get under 4.0.4 and 1.0.1 except then it would silently stall. Below are the only exceptions I got on the server. There was nothing in the log and none of my clients ever received and error.
anonymous wrote : 11:38:40,486 ERROR [SocketClientInvoker] Got marshalling exception, exiting
| java.io.IOException: Broken pipe
| at java.net.SocketOutputStream.socketWrite0(Native Method)
| at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
| at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
| at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
| at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
| at java.io.DataOutputStream.flush(DataOutputStream.java:106)
| at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:402)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:518)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:340)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
| at org.jboss.remoting.Client.invoke(Client.java:607)
| at org.jboss.remoting.Client.invoke(Client.java:599)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:637)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint$Deliverer.run(ServerConsumerEndpoint.java:637)
| at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
| at java.lang.Thread.run(Thread.java:619)
| 11:38:40,490 ERROR [ServerInvokerCallbackHandler] Error handling callback.
| java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
| java.io.IOException: Broken pipe
| at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:122)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:410)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
| at org.jboss.remoting.Client.invoke(Client.java:607)
| at org.jboss.remoting.Client.invoke(Client.java:599)
| at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:637)
| at org.jboss.jms.server.endpoint.ServerConsumerEndpoint$Deliverer.run(ServerConsumerEndpoint.java:637)
| at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.io.IOException: Broken pipe
| at java.net.SocketOutputStream.socketWrite0(Native Method)
| at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
| at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
| at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
| at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
| at java.io.DataOutputStream.flush(DataOutputStream.java:106)
| at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:402)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:518)
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:340)
| ... 7 more
| 11:38:40,496 WARN [ServerConsumerEndpoint] Failed to deliver the message to the client. See the server log for more details.
| 11:38:40,496 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client 1r6m4t1o-jfqhg5-ewi8w4zx-1-ewi8w6en-4. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed.
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3997994#3997994
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3997994
19 years, 3 months