This content has been marked as final.
Show 3 replies
-
1. Re: JBoss 7.1.1 remoting3-3.2.3 freeze (client failed with status WAITING)
sfcoy Oct 11, 2012 5:08 AM (in response to kmrol)1 of 1 people found this helpfulIt's possible that you have leaking resources.
I'd start with a thread dump of the "frozen" process to see if there's any hints there.
-
2. Re: JBoss 7.1.1 remoting3-3.2.3 freeze (client failed with status WAITING)
wdfink Oct 11, 2012 5:41 AM (in response to kmrol)Just to notice, there is an open issue that the threads get stuck if you have a ClassNotFoundEx during deserialization at client side AS7-4274.
-
3. Re: JBoss 7.1.1 remoting3-3.2.3 freeze (client failed with status WAITING)
kmrol Oct 11, 2012 6:14 AM (in response to sfcoy)Stephen, thanks for the thread dump advice, it's valueable for me. I'm not so sure that so "frozen" process which do not respond to kill signal will respond to kill -QUIT signal, but I'll try to do this next time.
Wold-Dieter Fink, it's hard to catch for me whether it was ClassNoFoundEx or not because there are too much clients and possibly one of the hundred got the ClassNotFoundEx before I got server "frozen".