Kbase P145126: OEE: AdminServer fails to re-start after adding CPU or memory resources
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  01/02/2010 |
|
Status: Verified
SYMPTOM(s):
AdminServer fails to re-start after adding CPU or memory resources
After successfully adding CPU or memory as Resources the icons disappear
Exception thrown when Loading project from Fathom configuration database. (11034)
Error starting Fathom probe: "Error loading configuration database: <installdir>\config\fathom.odb" (10148)
Fathom startup failed. (9661)
stack trace from java.exe reads:
Exception at : java.lang.NullPointerException
Message (throw): Error loading Fathom configuration database: [installdir]\config\fathom.odb
Message (excp): null
Stack Trace:
java.lang.NullPointerException
at java.lang.String.<init>(String.java:144)
at com.progress.isq.ipqos.resources.system.SystemResource.initResource(SystemResource.java:173)
Full stack trace from java.exe reads:
Exception at : com.progress.isq.ipqos.ProbeException
Message (throw): Error starting Fathom probe.
Message (excp): Error loading configuration database: [installdir]\config\fathom.odb
Stack Trace:
com.progress.isq.ipqos.ProbeException: Error loading configuration database: [installdir]\config\fathom.odb
at com.progress.isq.ipqos.Probe.loadProject(Probe.java:2135)
FACT(s) (Environment):
OpenEdge 10.1C03
OpenEdge 10.2A01
All Supported Operating Systems
OpenEdge Explorer
CAUSE:
This is a known issue. These options should not be available through the OpenEdge Explorer Console, only OpenEdge Management.
CAUSE:
Bug# OE00183507
FIX:
CPU and Memory resources have been removed from the OpenEdge Explorer view in OpenEdge 10.2A02 and 10.2B+. These options are not available to OpenEdge Explorer, only OpenEdge Management.
Workaround:
1. Ensure that the AdminServer is stopped - check for orphan java.exe and remove these
2. Open the [OpenEdge Explorer install]\config directory
3. delete the following files:
fathom.odx (this should not normally be present when the AdminServer is shut down)
fathom.odb, fathom.odf, fathom.odt
4. Start the AdminServer, the configuration database will be re-created