Fixes are available
APAR status
Closed as program error.
Error description
A NullPointerException can occur when a null namespace URI is passed to the SCA OperationTypeAdapter due to insufficient checking for this condition. In practical use, this error can occur if a customer uses WebService Binding with the following usage combination: -WSDL binding style doc-literal non-wrapped -null namespace parameter (DataObject) The error stack may contain the following: Caused by: java.lang.NullPointerException at com.ibm.wsspi.sca.scdl.impl.OperationTypeAdapterImpl.isJavaInter face(Ope rationTypeAdapterImpl.java:192) at com.ibm.ws.sca.internal.container.util.ContainerUtil.isJavaOpera tionType (ContainerUtil.java:100) at com.ibm.ws.sca.internal.jaxws.util.WebServiceLazyParsingUtil.mat chSOAPTo DataObject(WebServiceLazyParsingUtil.java:535) at com.ibm.ws.sca.internal.jaxws.util.WebServiceLazyParsingUtil.mat chInputF romSOAPToDataObject(WebServiceLazyParsingUtil.java:572) at com.ibm.ws.sca.internal.jaxws.util.WebServiceLazyParsingUtil.par seBody(W ebServiceLazyParsingUtil.java:718) at com.ibm.wsspi.sca.jaxws.data.JaxWsNativeDataHolder.getBody(JaxWs NativeDa taHolder.java:405)
Local fix
Workaround: Either change the WSDL to a different binding style (e.g. doc/lit wrapped) OR use non-null namespace for the parameter The error only occurs when both aspects of the problem are used together.
Problem summary
**************************************************************** * USERS AFFECTED: Users of Business Process Management * * Advanced * * Edition utilizing null namespace WSDL * * documents. * **************************************************************** * PROBLEM DESCRIPTION: When a null namespace is utilized in an * * SCA interaction, a NullPointerException * * may occur. * **************************************************************** * RECOMMENDATION: * **************************************************************** When a null namespace is utilized in an SCA interaction, a NullPointerException may occur due to no checking for a null condition when performing POJO evaluations.
Problem conclusion
To prevent the NullPointerException, the type checking code has been updating to check for the null condition prior to further checking.
Temporary fix
Comments
APAR Information
APAR number
JR43500
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-07-18
Closed date
2012-08-17
Last modified date
2012-08-17
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
BPM ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R750 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 October 2021