Kbase P119650: Fathom dies when trying to discover disk resources from initial configuration screen
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/03/2010 |
|
Status: Unverified
SYMPTOM(s):
Fathom dies when trying to discover disk resources from initial configuration screen
HTTP ERROR: 500 Exception for /management/gettingstartedvalidation.jsp
Unable to configure Fathom Management
Getting java.lang.IllegalArgumentException: empty name in BaseResource.setName when trying to configure Fathom
stacktrace reads:
java.lang.IllegalArgumentException: empty name in BaseResource.setName
at com.progress.isq.ipqos.ProjectStorage.StorageObject.setName(StorageObject.java(Compiled Code))
at com.progress.isq.ipqos.ProjectStorage.StorageObject.setName(StorageObject.java(Compiled Code))
at com.progress.isq.ipqos.resources.system.SystemResource.<init>(SystemResource.java:79)
at com.progress.isq.ipqos.resources.system.DiskResource.<init>(DiskResource.java:130)
at com.progress.isq.ipqos.resources.system.DiskResource.<init>(DiskResource.java:119)
at com.progress.isq.ipqos.plugin.FathomSystemConfiguration.createDiskResources(FathomSystemConfiguration.java:661)
at com.progress.isq.ipqos.plugin.FathomSystemConfiguration.getDiskResources(FathomSystemConfiguration.java:611)
at com.progress.isq.ipqos.plugin.FathomSystemConfiguration.setDiskIsMonitored(FathomSystemConfiguration.java:587)
at com.progress.isq.ipqos.plugin.FathomSystemConfiguration.setHardwareIsMonitored(FathomSystemConfiguration.java:413)
at com.progress.isq.ipqos.plugin.FathomSystemConfiguration.setHardwareResource(FathomSystemConfiguration.java:373)
Increasing java heap settings does not help
Disabling java compiler does not help
FACT(s) (Environment):
IBM AIX POWER 5.3 64-bit
OpenEdge 10.1A 64-bit
Fathom Management 3.1A 64-bit
CAUSE:
The exact cause is unknown at the time of this writing
FIX:
In order to get around the problem, please following these steps:
1) stop the AdminServer
2) delete FATHOM/config/fathom.o*
3) delete FATHOM/config/fathom.properties
4) start the AdminServer
5) access the Fathom Console (you will be back in main configuration screen)
6) on the 2nd screen, choose not to discover any disks
These steps will configure Fathom and you will be able to continue managing it.
Disks on the machine can be discovered later directly from the Fathom Console.