RE: [JBoss-user] Odd Problem...
Hey guys, Don't mean to be salesy and stuff but the way we like to deal with problems on systems in production is under a "production support contract". They start at 8k for one application. Not that we don't help for free, we do a lot of that for development and stuff. If you came here with a bug you solved on your time and a fix that would be one thing. Thanks Marcf PS: and I am not saying that because we just raised 10M of VC money > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Peter Luttrell > Sent: Wednesday, February 18, 2004 11:41 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Odd Problem... > > We experienced an odd problem last night in one of our > production servers running JBoss3.2.1 (with Jetty). The > entire things simply stopped responding for ~3 minutes! It > didn't complete any of it's web requests nor write anything > to the log for the entire period - something i've never seen before. > > The only thing that we can think of is that the VM was doing > GC for that period. Does anyone have any other ideas on what > could have caused the little nap it took? > > thanks. > .peter > > > -- > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments,is for the sole use of the intended recipient(s), > even if addressed incorrectly, and may contain confidential > and privileged information. Any unauthorized review, use, > disclosure or distribution is prohibited. If you are not the > intended recipient, please contact the sender by reply e-mail > and destroy or delete all copies of the original message and > all attachments, including deletion from the trash or > equivalent folder. Thank you. > > smime.p7s Description: S/MIME cryptographic signature
[JBoss-user] Odd Problem...
We experienced an odd problem last night in one of our production servers running JBoss3.2.1 (with Jetty). The entire things simply stopped responding for ~3 minutes! It didn't complete any of it's web requests nor write anything to the log for the entire period - something i've never seen before. The only thing that we can think of is that the VM was doing GC for that period. Does anyone have any other ideas on what could have caused the little nap it took? thanks. .peter -- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,is for the sole use of the intended recipient(s), even if addressed incorrectly, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy or delete all copies of the original message and all attachments, including deletion from the trash or equivalent folder. Thank you.
Re: [JBoss-user] odd problem...
On April 2, 2002 06:45 am, Jarecsni János wrote: > 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). You can shut down JBoss normally by http'ing to localhost:8082, and choosing the shutdown option. Optionally, you may also kill it by sending the '-INT' signal. i.e. kill -INT pid > 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. If you inspect this hung process a little closer (ps auxffww | grep java), you might find that it is not really JBoss, but a 'java -version' process, if you're running Sun's 1.3.x JVM. This did not occur on their 1.2.x JVM, and does not occur on their 1.4.x JVM. It also does not occur on IBM's JVM, or Blackdown's JVM. It's an incompatibility between those version of Sun's JVM and glibc's threading library from what I've been able to ascertain. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] odd problem...
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
