Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Several of our WebSphere ESB modules expose their interface as JAX-WS service (export). They invoke the Web services from different clients (other ESB modules, BPM Standard processes or even SoapUI) and fail with a runtime exception "Unable to resolve operation descriptor for jaxwsNoWSDLProviderOperation". There is a exception caught of retriving the WSDL&Schema files, Caused by: java.lang.RuntimeException: java.lang.NullPointerException at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(Sche maBuilder.java:1898) ...... at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(Sche maBuilder.java:1892) ... 52 more
Local fix
The problem is seen usually after a restart of the server where modules are deployed. Sometimes we also see this issue without any restart. The problem is consistent on all customer environments (development, staging, pre-prod, and very likely prod later on). The only way to fix the issue is a restart of the application/module; interestingly then the correct Web service operation can be called without any issue (we implemented a WAS scheduling job to do this task but this is only temporary solution).
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V8.0 and * * V8.5 users of JAX-WS Web Services * **************************************************************** * PROBLEM DESCRIPTION: When a server was loading multiple * * schema files with multiple threads, * * it could cause NullPointerException. * **************************************************************** * RECOMMENDATION: Install a fix pack containing this APAR. * **************************************************************** When the server was trying to load multiple schema files with multiple threads, there could be some non-thread-safe issues which cause a runtime exception with a NullPointerException. The following trace could be found in trace: Caused by: java.lang.RuntimeException: java.lang.NullPointerException at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(Sche maBuilder.java:1898) ...... at org.apache.ws.commons.schema.SchemaBuilder.resolveXmlSchema(Sche maBuilder.java:1892) ... 52 more
Problem conclusion
The non-thread-safe issue caused "null" to be used as the value of the schemaKey when a schema was cached, and "jaxwsNoWSDLProviderOperation" was set into Web Services metadata in the handler as the AxisOperation name. This APAR has changed this behavior and can handle the issue correctly. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.11 and 8.5.5.6. 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
PI32411
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-01-08
Closed date
2015-01-21
Last modified date
2016-03-31
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
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022