jboss-4.2.2.GA / jboss-messaging-1.4.0.SP3 / jboss-remoting-2.2.2.SP4 I see the folowing exception in the JBOSS console:
| 17:42:54,440 WARN [BisocketClientInvoker] 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:636) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) | My clients are standalone and they are implemented to survive cluster restarts (http://wiki.jboss.org/wiki/Wiki.jsp?page=JMSConnectionExceptionListener). The problem is that the clients do not get the exception callback at all - they are not aware that the pipe is broken and when I'm sending messages to the queue they do not receive anything. Is this the expected behaviour? I need my clients to try to reconnect endlessly if some network or other type of problem occures. (don;t know how to reproduce "Broken pipe") View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131750#4131750 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131750 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
