Unable to process control connection: Socket closed

[stephen.campbell]

Hi Guys,

I have recently added JBoss Messaging to my domain, and ever since this i seem to be getting a JBR error at intermidant points.

The error i am seeing is below :-

2007-06-01 09:24:57,473 INFO [STDOUT] 2007-06-01 09:24:57,471 ERROR [BisocketServerInvoker][[e-mail]][D965C3C5-DC4D-498F-3639-5D378B38D48B][myApp] - Unable to process control connection: Socket closed
java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at java.io.FilterInputStream.read(FilterInputStream.java:66)
at org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlConnectionThread.run(BisocketServerInvoker.java:598)

Ihave the same code running independantly on two machines, one is my PC for development work, which is then deployed onto a LInx box.

I do not see these errors in my PC, but do in the linx box ... ... weird !

Has anyone seen this behaviour before and if so, any ideas on how to fix it ???

Regards,
Stephen

[ron_sigal]

Hi Stephen,

Yeah, I just noticed this message - it's nothing. There's a test in org.jboss.remoting.transport.bisocket.BisocketServerInvoker that's meant to bypass this message, but I wrote

if ("socket closed".equals(e.getMessage())

instead of

if ("Socket closed".equals(e.getMessage())

It will get fixed in the next release. If you want to build your own jboss-remoting.jar, you should get the source from branch remoting_2_2_0_GA.

[stephen.campbell]

Hi Ron,

Thanks for the reply, glad it is something silly like that, puts my mind at ease a bit :o)

Have one question tho, is there a reason why this message would appear only in a Linx box, and not on my PC???

Regards,
Stephen