Troubleshooting
Problem
This issue is a change, which is introduced by JR36188 on WebSphere Process Server Versions 6.2.0.3 and 7.0.0.3. The code mistakenly believes a namespace is fully loaded and, thus, does not search for artifacts higher up in the class loader hierarchy. For example, it might not search in the ext jar classloader. This scenario might result in a NullPointerException exception within the trace.log file.
Symptom
You might see a warning message in the SystemOut.log file that is similar to the following text:
[12/1/10 2:11:44:645 EST] 00000382 BOCore W
EClassifier "http://www.mci.com/oagis/9#MCIMileStoneType" not found in
ClassLoaderScope: com.ibm.ws.classloader.
CompoundClassLoader@15521552
Local ClassPath: /opt/IBM/WAS/6.2/ProcServer/profiles/p2syst/
installedApps/p2ystNetwork/
SIPValidationBPC2ProcessApp_OMLOVO.ear/
SIPValidationBPC2ProcessEJB.jar:/opt/IBM/WAS/6.2/ProcServer/
profiles/p2syst/installedApps/p2ystNetwork/
SIPValidationBPC2ProcessApp_OMLOVO.ear/
SIPValidationBPC2Process.jar
Delegation Mode: PARENT_FIRST
Resolving The Problem
Apply JR38477.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21459885