APAR status
Closed as program error.
Error description
Client installed Maximo 7.6.0.1, deployed on WebSphere 8.5.5.3, Maximo runs fine, but this unexplained error and stack trace appear in SystemOut.log: [10/09/15 9:28:50:702 EDT] 0000006f SystemOut O starting repository auth service... [10/09/15 9:28:50:724 EDT] 0000006f SystemOut O 10 Sep 2015 09:28:50:721 [FATAL] [mxserver1] [] BMXAA6473E - The MXSERVER server could not be started. Check the log file for other errors to determine the cause. java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.lang.ClassNotFoundException: psdi.security.MaximoRepositoryAuthServiceRemote (no security manager: RMI class loader disabled) at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.jav a:417) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:2 65) at sun.rmi.transport.Transport$1.run(Transport.java:171) at java.security.AccessController.doPrivileged(AccessController.jav a:362) PROBLEM: Client finds inexplicable errors reported in his SystemOut.log. PERFORMANCE ISSUE: No STEPS TO REPRODUCE: Install Maximo 7.6. Apply 7.6.0.1 fixpack. Deploy on WebSphere 8.5.5. Login to Maximo. Note the errros being reported in SystemOut.log. CURRENT ERRONEOUS RESULT: Found in SystemOut.log: [10/09/15 9:28:50:702 EDT] 0000006f SystemOut O starting repository auth service... [10/09/15 9:28:50:724 EDT] 0000006f SystemOut O 10 Sep 2015 09:28:50:721 [FATAL] [mxserver1] [] BMXAA6473E - The MXSERVER server could not be started. Check the log file for other errors to determine the cause. java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.lang.ClassNotFoundException: psdi.security.MaximoRepositoryAuthServiceRemote (no security manager: RMI class loader disabled) at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.jav a:417) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:2 65) at sun.rmi.transport.Transport$1.run(Transport.java:171) at java.security.AccessController.doPrivileged(AccessController.jav a:362) EXPECTED RESULT: There should be no errors displayed to SystemOut.log. ADDITIONAL INFO: Client reports that Maximo works fine. He finds the errores eported to SystemOut unacceptable and requests a fix. Note: seems there is no RMI stub file for MaximoRepositoryAuthServiceRemote class. Issue is reproduced in house. Fix is needed for 7.6.0.1 and 7.6.0.2. ENVIRONMENT (SYSTEM INFO): Windows, Maximo 7.6.0.1, WebSphere 8.5.5.3. LOCAL FIX: It seems there are no errors when RMIRegistry is stopped.
Local fix
It seems there are no errors when RMIRegistry is stopped. There is no impact on Maximo. Able to login and use the apps with no issues or performance degradation. Need to resolve issue to avoid client calls.
Problem summary
**************************************************************** * USERS AFFECTED: * * All Maximo Users. * **************************************************************** * PROBLEM DESCRIPTION: * * ClassNotFoundException: * * psdi.security.MaximoRepositoryAuthServiceRemote is displayed * * in SystemOut.log. * **************************************************************** * RECOMMENDATION: * * Upgrade to latest release. * **************************************************************** ERROR DESCRIPTION: Client installed Maximo 7.6.0.1, deployed on WebSphere 8.5.5.3, Maximo runs fine, but this unexplained error and stack trace appear in SystemOut.log: [10/09/15 9:28:50:702 EDT] 0000006f SystemOut O starting repository auth service... [10/09/15 9:28:50:724 EDT] 0000006f SystemOut O 10 Sep 2015 09:28:50:721 [FATAL] [mxserver1] [] BMXAA6473E - The MXSERVER server could not be started. Check the log file for other errors to determine the cause. java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.lang.ClassNotFoundException: psdi.security.MaximoRepositoryAuthServiceRemote (no security manager: RMI class loader disabled) at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.jav a:417) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:2 65) at sun.rmi.transport.Transport$1.run(Transport.java:171) at java.security.AccessController.doPrivileged(AccessController.jav a:362) PROBLEM: Client finds inexplicable errors reported in his SystemOut.log. PERFORMANCE ISSUE: No STEPS TO REPRODUCE: Install Maximo 7.6. Apply 7.6.0.1 fixpack. Deploy on WebSphere 8.5.5. Login to Maximo. Note the errros being reported in SystemOut.log. CURRENT ERRONEOUS RESULT: Error found in SystemOut.log. EXPECTED RESULT: There should be no errors displayed to SystemOut.log. ADDITIONAL INFO: Client reports that Maximo works fine. He finds the errors reported to SystemOut unacceptable and requests a fix. ENVIRONMENT (SYSTEM INFO): Windows, Maximo 7.6.0.1, WebSphere 8.5.5.3. LOCAL FIX: It seems there are no errors when RMIRegistry is stopped.
Problem conclusion
ClassNotFoundException: psdi.security.MaximoRepositoryAuthServiceRemote is not displayed in SystemOut.log. The fix for this APAR is contained in the following maintenance package: | release\fix pack | Fix Pack Release 7.6.0.4 TPAE
Temporary fix
Comments
APAR Information
APAR number
IV78477
Reported component name
MAXIMO SYSTEMS
Reported component ID
5724R46AV
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-10-29
Closed date
2015-12-15
Last modified date
2015-12-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
MAXIMO
Fix information
Fixed component name
MAXIMO SYSTEMS
Fixed component ID
5724R46AV
Applicable component levels
R760 PSY
UP
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPP5","label":"System Related"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
15 December 2015