Kbase P106819: AdminServer appears to stop and AppServer broker does not start after upgrading AIX 5.2 ML4 to ML6
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  9/29/2008 |
|
Status: Verified
SYMPTOM(s):
AppServer broker does not start after upgrading AIX 5.2 ML4 to ML6
Fathom Management is installed but monitoring is disabled
AdminServer started successfully but then appeared to stop after loading the osmetrics.dll
No errors in the admsrv.log file
AppServer broker log file has multiple errors regarding server not starting.
Message from server : Startup Procedure Failed (8113)
IOException reading message from server : java.io.EOFException: pipe to server broken (8117)
ERROR: cannot start server. (8100)
Exception unbinding broker (not bound) : ExceptionMsg_string (8525)
Application server log file has errors indicating that there is no server for the database.
** There is no server active for database <database> on -H <hostname> -S <servicename>. (704)
Error initializing the application server. (5479)
Java core file produced with time stamp shortly after last entry in admserv.log
SIGSEGV received at 0xd3139184 in /usr/local/dlc10b/bin/osmetrics.dll. Processing terminated.
Native Stack:
3XHSTACKLINE at 0xD31399EC in RefreshInstanceList__10CAmsObjectFv
3XHSTACKLINE at 0xD3139274 in __ct__10CAmsObjectFPCc
3XHSTACKLINE at 0xD31289DC in CreateObjects__8CAmsMainFv
3XHSTACKLINE at 0xD31225B4 in InitLibrary__FPCc
3XHSTACKLINE at 0xD31229B8 in Java_com_progress_osmetrics_OSMetricsImpl_jniInitLibrary
No ProcInfo in the foot print of the stack.
FACT(s) (Environment):
OpenEdge 10.0B
IBM AIX POWER 5.2
CHANGE:
Java version changed from 1.4.16 to 1.4.2
CHANGE:
Upgraded AIX 5.2 Maintenance Release from ML 4 to ML 6
CAUSE:
Bug# OE00114161
FIX:
Upgrade to 9.1E02 or later, 10.0B02 or later and 10.1A.