Eliminate unnecessary "Unable to process control connection:" message from BisocketServerInvoker ------------------------------------------------------------------------------------------------ Key: JBREM-751 URL: http://jira.jboss.com/jira/browse/JBREM-751 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.4.0.Beta1 (Pinto) In org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(), there is a try/catch block that catches IOExceptions. If the IOException is caused by a closed socket, then the thread quietly shuts down, instead of logging an error. However, the test "socket closed".equals(e.getMessage()) should have been "Socket closed".equals(e.getMessage()), and so an error is sometimes logged unnecessarily. -- 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