Kbase P110838: AdminServer hangs on shutdown on Linux when Fathom remote monitoring is enabled
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/15/2005 |
|
Status: Unverified
FACT(s) (Environment):
Linux Intel
Progress 9.1D
Progress 9.1E
Fathom Management 2.1A
Fathom Management 3.0A
SYMPTOM(s):
AdminServer hangs on shutdown on Linux
Fathom remote monitoring is enabled
Using JVM 1.3.X
Unable to stop Fathom AdminServer on Linux
Without remote monitoring AdminServer stops just fine
CAUSE:
This is an expected behavior, eg it's a bug in SUN JVM 1.3.X
FIX:
On a Linux platform, running Fathom with remote monitoring enabled requires an environment variable to be set to prevent the AdminServer from hanging on shutdown. The environment variable J2SE_PREEMPTCLOSE=1 must be set prior to starting the AdminServer. This environment setting enables a workaround in the 1.3.1 JVM that works with RedHat versions prior to 7.3. RedHat versions 7.3 and later are not compatible with this workaround and the AdminServer will fail to start if it is used.
The following two Sun JAVA bugs detail the JVM problem:
Sun Java Bug 4344135:
Linux: close is not preemptive
http://developer.java.sun.com/developer/bugParade/bugs/4344135.html
Sun Java Bug 4866511:
With J2SE_PREEMPTCLOSE=1 set, 1.3.1_xx broken on RH7.3 and up
http://developer.java.sun.com/developer/bugParade/bugs/4866511.html
For Linuxes unable to use the environment variable, the only way how to stop (and start) the adminserver now would be to kill the 2 remaining (Sonic) java processes (after proadsv -stop was issued), delete the Sonic lock files
rm -rf $FATHOM/SonicMQ/Fathom1/data/_MFSystem/lock
rm -rf $FATHOM/SonicMQ/SonicMQDB/db.lck
and restart the AdminServer.
Another workaround would be to upgrade to JVM 1.4 (as the JVM issues are fixed there), but this would require to move to OE 10.0B (or higher), at least on the Fathom AdminServer side, since 9.1X does not support JVM 1.4.