Fix (APAR):  PI32411

Status:  Fix

Release:  8.0.0.7

Operating System:  AIX,HP-UX,IBM i,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  269296

Date: 2022-07-07

Abstract:  bpm receives nullpointerexception due to jaxwsnowsdlprovideroperation

Description/symptom of problem:  
PI32411 resolves the following problem:

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   


Directions to apply fix:  
NOTE: Mark with an X the:
1) Release the fix applies to
2) The Editions that apply
3) And then DELETE THIS NOTE

Fix applies to Editions:
Release 8.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Knowledge Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: