[
http://jira.jboss.com/jira/browse/JBMESSAGING-974?page=all ]
Tim Fox updated JBMESSAGING-974:
--------------------------------
Fix Version/s: 1.4.0.CR1
(was: 1.3.0.GA)
Priority: Minor (was: Major)
Apparently this is a benign error, and Ron just needs to stop the logging.
This will be fixed in the next release of JBR (SP5?)
Unable to process control connection
------------------------------------
Key: JBMESSAGING-974
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-974
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Ron Sigal
Priority: Minor
Fix For: 1.4.0.CR1
When running messaging remote tests (ant remote-tests from tests dir).
At various points, JBoss Remoting is logging the following:
[junit] @control: Socket[addr=/127.0.0.1,port=2960,localport=58358] 17:09:54,929 ERROR
[BisocketServerInvoker] Unable to process control connection: Socket closed
[junit] java.net.SocketException: Socket closed
[junit] at java.net.SocketInputStream.socketRead0(Native Method)
[junit] at java.net.SocketInputStream.read(SocketInputStream.java:129)
[junit] at java.net.SocketInputStream.read(SocketInputStream.java:182)
[junit] at java.io.FilterInputStream.read(FilterInputStream.java:66)
[junit] at
org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(BisocketServerInvoker.java:652)
This doesn't seem to cause the tests to fail, and is annoying.
I guess remoting is trying to clear up its state and failing (??)
--
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