[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
10.03.2003 15:57
Please respond to jboss-user
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: [JBoss-user] Neglected JBoss 3.0.5 falls into a coma
> Lastly, is there a
> Lastly, is there a clever way to generate a stacktrace dump?
> Our JBoss
> server process was started in the background, and then I
> logged out. Can
> this be done with the JMX-Console? Is there a handy MBean to
At least there is a topic in the http-version, so I assume you can
do the same
+353 1 872 3305
Mobile: +353 86 824 0736
"Sacha Labourey" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
10.03.2003 12:52
Please respond to jboss-user
To: <[EMAIL PROTECTED]>
cc:
Subject: RE: [JBoss-user] Neglected JBoss 3.0
heers,
Sacha
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Jonathan.O'[EMAIL PROTECTED]
> Sent: lundi, 10. mars 2003 12:34
> To: [EMAIL PROTECTED]
> Subject: [JBoss-user] Neglected JBoss 3.0.5 falls into a com
We noticed a worrying feature of JBoss 3.0.4 and 3.0.5 recently. If JBoss
is started, and then not used for maybe a day or two, it goes into a coma.
we are running this on Linux, with Java 1.4 JVM. The processes are still
there, but it won't respond to requests from the web (via Jetty) or client
