Hi,

recently I've run into a rather odd problem which seems quite impossible to
track down.

The configuration is JBoss244+Tomcat401 with Apache (1.3.22) on a Debian
Linux 2.4.3
The problem is that JBoss hangs after a few days of operation. By "hangs" I
mean that it does not accept any new request, and stays so until it is
killed. This killing is rather peculiar too: I ask for the process list
pertaining to JBoss by issuing: "ps aux | grep jboss". From the list I
choose one and kill it with -9. It usually brings down JBoss at one (you see
"killed" in the log). The only problem is that there remains one process
that cannot be killed. And because of that sole process I have to restart
the machine (otherwise I can't start JBoss because it cannot start listen on
a port).

Now I suspect that this process is responsible for what's happening. It
seems something like a dead lock. I cannot image what's causing this. What I
know is this has nothing to do with server load, server hangs no matter how
many are using it. Do you have any ideas? How should I start unfolding this
problem? BTW: the same application worked for weeks without stopping on
JB241TC323. Of course, the application code has changed in the meantime, so
if the error is lurking in the app code somewhere then it won't work on
earlier JBoss either.

Thanks in advance,
János


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to