PK93756: ENABLE USE OF THIRD PARTY JAX-WS WEB SERVICES ENGINE IN WEBSPHERE

Fixes are available

APAR status

Closed as new function.

Error description

The WebSphere Application Server provides a JAX-WS Web Service
engine. Some customers may choose to use a different,
third-party JAX-WS engine.

Customers who use a different JAX-WS engine may see the
following problems:
1) The application build on third party JAX-WS runtime may
fail to start.

2) Customers may see the following error in FFDC logs during
runtime:

javax.servlet.ServletException:
org.apache.axis2.AxisFault: The system is attempting to engage
a module that is not available: addressing
 at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(Ax
isServlet.java:523)
 at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.jav
a:436)

3) Customers may see the following runtime exception in the
trace log:

java.lang.ClassCastException:
org.apache.cxf.transport.servlet.CXFServlet incompatible with
javax.servlet.Servlet
 at
com.ibm.ws.webcontainer.servlet.ServletWrapper$1.run(ServletWrap
per.java:1392)
 at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
troller.java:118)
 at
com.ibm.ws.webcontainer.servlet.ServletWrapper.loadServlet(Servl
etWrapper.java:1387)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users who wish *
*                  to deploy and run web service applications  *
*                  which use external JAX-WS engines           *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server            *
*                      applications cannot be deployed when    *
*                      those applications attempt to use an    *
*                      external JAX-WS engine                  *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR     *
*                  and follow Information Center instructions  *
*                  to perform mandatory configuration changes  *
*                  to allow applications with external JAX-WS  *
*                  implementations to work correctly.          *
****************************************************************
The customer is unable to deploy JAX-WS applications on a
WebSphere Application Server when the application contains
an external JAX-WS engine. (Example external JAX-WS engines
are Apache Axis2, Apache CXF.)

Here is an example error:

Caused by: java.lang.Error: javax.xml.soap.SOAPException:
Unable to create SAAJ
meta-factoryorg.apache.axis2.saaj.SAAJMetaFactoryImpl:
imcompatible with javax.xmlo.soap.SAAJMetaFactory

  at com.sun.xml.internal
ws.spi.SOAPVersion.<init>(SOAPVersion.java:144)
  at
com.sun.xml.internal.ws.spi.SOAPVersion.<clinit>(SOAPVersion.jav
a:68)
  at java.lang.J9VMInternals.initializeImpl(Native Method)
  at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)

The most notable problem is that the default JAX-WS web
services engine is not being properly disabled when an external
engine is being used. It appears to be conflicting with the
third party implementation.

The customer should be able to use a third party JAX-WS
implementation jars from the application library.

Problem conclusion

A solution is provided that will allow the customer to disable
the IBM JAX-WS engine and then enable the third party JAX-WS
engine.

NOTE: IBM does not claim support for any third party JAX-WS
engines.

New properties are added to the WebSphere Application Server to
allow a user to disable the WebSphere Application Server's
JAX-WS engine.

To Disable the JAX-WS Engine:
------------------------------
There are two ways that a customer can disable the JAX-WS
Engine:

1)Edit the module?s WebContent/META-INF/ MANIFEST.MF file.
Add the following property;
DisableIBMJAXWSEngine: true
2) Or, Set the following JVM property
com.ibm.websphere.webservices.DisableIBMJAXWSEngine=true

The following Information Center topic describes how to set
a JVM property:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
topic=/com.ibm.websphere.nd.iseries.doc/info/iseriesnd/ae/trun_j
vm.html

For unmanaged WebSphere Application Server clients,set the
property using a java option:
-Dcom.ibm.websphere.webservices.DisableIBMJAXWSEngine=true


To Enable the Third Party JAX-WS Engine:
----------------------------------------
In order for customers to enable an external JAX-WS runtime in
their application they will have to change the ClassLoader
Policy at the module level. For WebSphere Application Server
7.0 this policy needs to be set to ?Classes loaded with local
class loader first (parent last)?.  The following
Information Center topic describes the ClassLoader Policy
settings:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
topic=/com.ibm.websphere.soafep.multiplatform.doc/info/ae/ae/cru
n_classload.html

Troubleshooting
---------------

After disabling the IBM JAX-WS engine and enabling the third
party JAX-WS engine, a customer may still encounter problems.
Use the the Information Center documentation to troubleshoot
issues.
Here are some of the issues a customer may face:

1) Jar file conflicts
2) Incompatible JAXP implementation
3) Incompatible Transform Factory implementations
3) Commons Logging issues

Restrictions
------------

The customer will still need to be aware of following
restrictions:
1. If an application (with a third party JAX-WS engine)
contains a conflicting jar file, it will have to be removed
from their application library (as documented in
Information Center).
Most of the external third party JAX-WS engines include various
jar libraries.  Some of these libraries are already loaded by
the WebSphere Application Server's implementation, which may
cause conflicts.

2. Users will not be able to use both the IBM JAX-WS
engine and an external third party engine in the same
application.


The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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 number
PK93756
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-12
Closed date
2009-09-04
Last modified date
2009-09-04

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

PK96369 PK96989

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK93756: ENABLE USE OF THIRD PARTY JAX-WS WEB SERVICES ENGINE IN WEBSPHERE

Fixes are available

Subscribe

APAR status

Closed as new function.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?