[jboss-user] [JNDI and Naming] - JBoss 7.1.1 remoting3-3.2.3 freeze (client failed with status WAITING)

Kirill Mikhailov do-not-reply at jboss.com
Wed Oct 10 23:30:51 EDT 2012

Kirill Mikhailov [https://community.jboss.org/people/kmrol] created the discussion

"JBoss 7.1.1 remoting3-3.2.3 freeze (client failed with status WAITING)"

To view the discussion, visit: https://community.jboss.org/message/764222#764222

Hello everybody!
We got JBoss 7.1.1 freezed after 1-2 days of production load. Client get NamingException with "Operation failed with status WAITING". The jboss java process (on Solaris SPARC) did not stop by regular kill (only kill -9) and the server.log did not show any exception and did not show stop messages (default logging in standalone.xml with no trace turned on).

After reading  https://issues.jboss.org/browse/AS7-5249 AS7-5249 we have update org.jboss.remoting3 module from 3.2.3 to 3.2.8 and after 2 days on the clients again got the same NamingException with status WAITING and no exception on the server.log but in this case the server process had wrote stop messages while stopping JBoss (kill ok). Next time we turn on trace on all categories and update remoting3 module to 3.2.10 version. After that JBoss is working ok on the same production load.

I don't know what was the cause of the freezings but surely update to remoting3 version 3.2.1 helps to fix it.

Reply to this message by going to Community

Start a new discussion in JNDI and Naming at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20121010/c270bab8/attachment.html 

More information about the jboss-user mailing list