Fix (APAR): JR31654 Status: Fix Release: 6.1.0.2 Operating System: i5/OS,Linux,Windows,z/OS Supersedes Fixes: CMVC Defect: JR31654 Byte size of APAR: 13060 Date: 2009-02-18 Abstract: Deadlocks will occur when parsing business objects (BO). Description/symptom of problem: JR31654 resolves the following problem: ERROR DESCRIPTION:? Customer is getting a deadlock situation. The following WPS code might be the root cause of this deadlock situation. Error stack trace related to WPS: com/ibm/wbiserver/mediation/ifm/InterfaceMediationHandler$2.run( InterfaceMediationHandler.java:137) com/ibm/wbiserver/mediation/ifm/InterfaceMediationHandler.loadIF MInstance(InterfaceMediationHandler.java:133) com/ibm/wbiserver/mediation/ifm/InterfaceMediationHandler.getIFM Handler(InterfaceMediationHandler.java:207(Compiled Code)) com/ibm/wbiserver/mediation/MediationContext.(MediationCon text.java:90(Compiled Code)) com/ibm/wbiserver/mediation/MediationImplementationHandler.proce ssMessage(MediationImplementationHandler.java:286(Compiled Code)) From the javacore files we see: ______________________________________________ 3XMTHREADINFO "Default : 4" (TID:0x0000000008A8F800, sys_thread_t:0x0000000008A8EC28, state:B, native ID:0x00000000000010E6) prio=5 4XESTACKTRACE at java/lang/ClassLoader.loadClass(ClassLoader.java:597(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/impl/dv/ObjectFactory.findProviderClass(Byteco de PC:55(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/impl/dv/ObjectFactory.newInstance(Bytecode PC:3(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/impl/dv/DTDDVFactory.getInstance(Bytecode PC:5(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/impl/dv/DTDDVFactory.getInstance(Bytecode PC:2(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/XML11Configuration.(Bytecode PC:815(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/XIncludeAwareParserConfiguration.(Byteco de PC:4(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/XIncludeAwareParserConfiguration.(Byteco de PC:4(Compiled Code)) 4XESTACKTRACE at java/lang/Class.newInstancePrototype(Class.java:1339(Compiled Code)) 4XESTACKTRACE at java/lang/Class.newInstance(Class.java:1328(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/ObjectFactory.newInstance(Bytecode PC:6(Compiled Code)) waiting on 3XMTHREADINFO "Default : 5" (TID:0x000000000B154500, sys_thread_t:0x00002AAB82314C80, state:B, native ID:0x00000000000010E7) prio=5 4XESTACKTRACE at org/apache/xerces/parsers/XML11Configuration.(Bytecode PC:815(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/XIncludeAwareParserConfiguration.(Byteco de PC:4(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/XIncludeAwareParserConfiguration.(Byteco de PC:4(Compiled Code)) 4XESTACKTRACE at java/lang/Class.newInstancePrototype(Class.java:1339(Compiled Code)) 4XESTACKTRACE at java/lang/Class.newInstance(Class.java:1328(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/ObjectFactory.newInstance(Bytecode PC:6(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/ObjectFactory.createObject(Bytecode PC:529(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/ObjectFactory.createObject(Bytecode PC:3(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/SAXParser.(Bytecode PC:3(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/parsers/SAXParser.(Bytecode PC:3(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/jaxp/SAXParserImpl$JAXPSAXParser.(Byteco de PC:3(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/jaxp/SAXParserImpl$JAXPSAXParser.(Byteco de PC:2(Compiled Code)) 4XESTACKTRACE at org/apache/xerces/jaxp/SAXParserImpl.(Bytecode PC:2(Compiled Code)) ____________________________________________________________ LOCAL FIX:? N/A PROBLEM SUMMARY:? USERS AFFECTED: WebSphere Process Server v6.1.0.x, v6.1.2.x, and v6.2.0.0 users. PROBLEM DESCRIPTION: Deadlocks will occur when parsing business objects (BO). RECOMMENDATION: None Problem caused synchronization deadlocks. PROBLEM CONCLUSION:? Applying this interim fix will resolve the issue. Directions to apply fix: Download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Process Server. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed 1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Process Server. Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server. Additional Information: