JMS server 2.4.3 hung with the Socket Interrupted System Cal

[ptran83]

Hi,

Is anybody experienced the JMS server hung with the interrupted system call on Solaris 8.0 server? When this happens, the JMS client will block when perfom connection i.e, topicFactory.createTopicConnection(). Restart the JBOSS server, the client will successfully connected. Attached is the stack trace:

[OILServerILService] Could not initialize the OILServerIL Service.\par
java.net.SocketException: Interrupted system call\par
at java.net.PlainSocketImpl.socketAccept(Native Method)\par
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:468)\par
at java.net.ServerSocket.implAccept(ServerSocket.java:243)\par
at java.net.ServerSocket.accept(ServerSocket.java:222)\par
at org.jboss.mq.il.oil.OILServerILService.run(OILServerILService.java:174)\par
at java.lang.Thread.run(Thread.java:484)\par


Thanks for your info.

Peter

[msquance]

Hi,

I have just experienced this problem as well. I found that restarting the OIL service through JMX was enough to release the hanging.

This was running JBoss 2.4.9 on Solaris 8 (Java HotSpot(TM) Server VM (build 1.3.1_04-b02, mixed mode))

I have also experienced hanging problems with JMS on Digital Unix, but restarting the OIL service does not help (and I don't get any errors from JMS). I am able to reproduce the problem much easier on Digital Unix and am currently trying to simplify the scenario to the extent that I can supply some reproducing code to the JBoss folks.

My initial feeling is that there is something not thread safe in the topic subscriber receive call. I find that I can reproduce the problem easier when I make receive calls that only block for 1 second and then come back in. The hanging seems to occur when two threads make the receive call at the same time.

As I said, I hope to supply more detailed information sometime soon.

Regards,
Mike.