[esb-issues] [JBoss JIRA] Created: (JBESB-692) WARN [BisocketClientInvoker] Message when using bootstrapper

WARN [BisocketClientInvoker] Message when using bootstrapper ------------------------------------------------------------ Key: JBESB-692 URL: http://jira.jboss.com/jira/browse/JBESB-692 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Priority: Minor Fix For: 4.2 The following warning & stack trace show up on the AS console whenever you "Ctrl-C" the bootstrapper. 15:31:36,109 WARN [BisocketClientInvoker] Unable to send ping: shutting down Pi ngTimerTask 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$PingTimer Task.run(BisocketClientInvoker.java:497) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) To recreate: quickstart helloworld 'ant deploy-jms-dests' 'ant run' Ctrl-C The message pops up on the console. Either we need to fix whatever is in the bootstrapper that JBoss Messaging doesn't like (disconnection must be improper) or we need to turn off this warning level. Additional warnings sometimes appear as well: 15:34:53,593 WARN [SimpleConnectionManager] ConnectionManager[c2b246] cannot lo ok up remoting session ID 5c4o22-n5wjzb-f44hz8li-1-f44hz8ze-4 15:34:53,593 WARN [SimpleConnectionManager] A problem has been detected with th e connection to remote client 5c4o22-n5wjzb-f44hz8li-1-f44hz8ze-4. It is possibl e 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira