PM45109: CWWSS5007E ERROR WHEN LOADING CLASSES WITH JAX-WS WS-SECURITY

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• JAX-WS WS-Security may get a CWWSS5007E error when it tries to
  load application classes such as token generators and
  consumers:
  
  CWWSS5007E: Class "com.acme.wssec.myGenerator" not found.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server Feature    *
  *                  Pack for Web Services users of WS-Security  *
  *                  enabled JAX-WS applications                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: CWWSS5007E error may occur when         *
  *                      JAX-WS WS-Security loads application    *
  *                      classes                                 *
  ****************************************************************
  * RECOMMENDATION:  Install a fix pack that includes this       *
  *                  APAR.                                       *
  ****************************************************************
  Classes belonging to a web services application that are
  configured in the WS-Security JAX-WS policy bindings
  may not load properly.  When this happens, a message similar
  to the following appears in the trace, ffdc and SystemOut.log:
  CWWSS5007E: Class "com.acme.wssec.myGenerator" not found.
  The classes include, but are not limited to custom token
  generators and consumers and custom JAAS login modules.
  

Problem conclusion

• The WS-Security runtime is using the class loader that
  originaly loaded the com.ibm.xml.soapsec.util.ConfigUtil class
  instead of the context class loader to load all classes.  This
  can cause the runtime to not be able to locate some classes
  that belong to an application program.
  
  The WS-Security runtime is updated to attempt to load classes
  with the context class loader.
  
  To maintain the original behavior, the WS-Security runtime
  will first attempt to load classes with the class loader that
  loaded the ConfigUtil class.  If the first class loader cannot
  load the class, the runtime will then attempt to use the
  context class loader.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.1.0.43.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

  PM30683

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

Fix information

• Fixed component name

  WEBSERVIC FEATU

• Fixed component ID

  5724J0850

Applicable component levels

• R610 PSY

     UP