PH43152: RUNTIME MODULE CODE DOESN'T HAVE THE NECESSARY THREAD CONTEXT PROTECTION.

APAR status

• Closed as program error.

Error description

• runtime module code doesn't have the necessary thread context
  protection.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A ClassCastException in JAXP can occur  *
  *                      while starting an application when      *
  *                      parent-last class loader delegation is  *
  *                      used                                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When an environment utilizes parent-last class loading, and the
  parent-last loader contains a JAXP API and implementation, the
  following exception can occur while starting the application:
  [8/30/21 12:35:41:240 CEST] 0000004f SharedEJBRunt E
  WSVR0040E: addEjbModule failed for ejbJar.jar
  javax.xml.parsers.FactoryConfigurationError: Provider
  javax.xml.parsers.DocumentBuilderFactory could not be
  instantiated: java.util.ServiceConfigurationError:
  javax.xml.parsers.DocumentBuilderFactory: Provider
  org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not a subtype
  at
  javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown
  Source)
  at
  com.ibm.ejs.models.base.extensions.helper.CommonExtensionsHelper
  .getInputStream(CommonExtensionsHelper.java:160)
  This occurs because the WAS server runtime has not adequately
  protected its thread context class loader before attempting to
  instantiate an XML parser. At the point of failure, the thread
  context class loader is the application's loader, and in the
  problematic configuration, the server mistakenly links to the
  application's instance of JAXP instead of its own.
  

Problem conclusion

• Thread context protection was added to the WAS code that loads t
  deployment descriptor.
  
  The fix for this APAR is targeted for inclusion in fix packs
  9.0.5.13 and 8.5.5.23. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

• Remove the XML API jar(s) from the parent-last application or
  shared library, or set class loader delegation to parent-first
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels