Weblogic server 10.0 - Managed Server shutting down?

Since you are using Xnohup option, the JVM is very likely not receiving an OS signal. Still, something is triggering the shutdown (and the fact that it happens at very regular intervals suggests an automated process) Try to apply the second suggestion of this blog post (I think that this come from the support actually): If the issue recurs again even after trying the above option then can you please apply the following JAVA_OPTION : Depending on the JVM version, it may be possible to get a thread dump before the process exits HotSpot supports the command-line option XX:+ShowMessageBoxOnError The corresponding JRockit option is Djrockit. Waitonerror While the JVM goes down, it may prompt the user: "Do you want to debug the problem?

This pauses the JVM, thereby creating an opportunity to generate a thread dump (a stack trace of every thread in the JVM), attach a debugger, or perform some other debugging activity To generate a thread dump, I think that you'll have to remove the Xnohup option (this shouldn't be a problem since it doesn't help). This would really help the analysis Also open a case, the support might have more input on this (you're not the only one facing this problem, see the mentioned threads below) Just in case, have a look at WebLogic Server shutting down Automatically (any watchdog process OOMKiller running? ) and JVM called WLS shutdown hook.

The server will force shutdown now.

Since you are using -Xnohup option, the JVM is very likely not receiving an OS signal. Still, something is triggering the shutdown (and the fact that it happens at very regular intervals suggests an automated process). Try to apply the second suggestion of this blog post (I think that this come from the support actually): If the issue recurs again even after trying the above option then can you please apply the following JAVA_OPTION: Depending on the JVM version, it may be possible to get a thread dump before the process exits HotSpot supports the command-line option -XX:+ShowMessageBoxOnError The corresponding JRockit option is -Djrockit.

Waitonerror While the JVM goes down, it may prompt the user: "Do you want to debug the problem? " This pauses the JVM, thereby creating an opportunity to generate a thread dump (a stack trace of every thread in the JVM), attach a debugger, or perform some other debugging activity. To generate a thread dump, I think that you'll have to remove the -Xnohup option (this shouldn't be a problem since it doesn't help).

This would really help the analysis. Also open a case, the support might have more input on this (you're not the only one facing this problem, see the mentioned threads below). Just in case, have a look at WebLogic Server shutting down Automatically (any watchdog process OOMKiller running?) and JVM called WLS shutdown hook.

The server will force shutdown now.

I tried using -Djrockit. Waitonerror, but JVM does not pause. I also see the following "panic" message in the log either just before or few minutes before.

CharScanner; panic: ClassNotFoundException: org.antlr.stringtemplate.language. ChunkToken Looks like this during some kind of Diagnostics run: – Eqbal Mar 17 '10 at 22:57 @Eqbal Why don't you put this in your question? This may help.

– Pascal Thivent Mar 17 '10 at 23:17 Thanks, I just updated the question. – Eqbal Mar 17 '10 at 23:28.

Conflict with weblogic's antlr version and the one used in the deployed app (war). Included that war in an ear file and put a weblogic-application. Xml file in META-INF with the following: antlr.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.