APAR status
Closed as program error.
Error description
The SOAPInput node issues a BIP3701E error message if the associated WSDL file does not have a target namespace. The exception generated is: BIP3701E: A Java exception was thrown whilst calling the Java JNI method ''method_com_ibm_broker_axis2_SoapParserUtil_getInboundContext'' . The Java exception was ''java.lang.NullPointerException''. The Java stack trace was ''Frame : 0 java.lang.NullPointerException: null| @:com.ibm.broker.axis2.SoapParserUtil.getInboundContext(Unknown Source)|''. Correct the error, and if necessary redeploy the flow. : /build/S1000_slot1/S1000_P/src/WebServices/WSLibrary/ImbSOAPPars er.cpp: 1771: ImbSOAPParser::createSoapShapedTree: : If ?wsdl is attempted on the URL of the SOAPInput node where the WSDL does not have a target namespace, then "no service data available" is returned instead of the WSDL.
Local fix
N/A
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V10.0 who use the SOAPInput node and have a wsdl with no target namespace. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The SOAPInput node issues a BIP3701E error message if the associated WSDL file does not have a target namespace. The exception generated is: BIP3701E: A Java exception was thrown whilst calling the Java JNI method ''method_com_ibm_broker_axis2_SoapParserUtil_getInboundContext'' . The Java exception was ''java.lang.NullPointerException''. The Java stack trace was ''Frame : 0 java.lang.NullPointerException: null| @:com.ibm.broker.axis2.SoapParserUtil.getInboundContext(Unknown Source)|''. Correct the error, and if necessary redeploy the flow. : /build/S1000_slot1/S1000_P/src/WebServices/WSLibrary/ImbSOAPPars er.cpp: 1771: ImbSOAPParser::createSoapShapedTree: : If ?wsdl is attempted on the URL of the SOAPInput node where the WSDL does not have a target namespace then "no service data available" is returned instead of the WSDL. There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
The product now handles wsdl with no target namespace without errors. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.5 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT13662
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-08
Closed date
2016-05-25
Last modified date
2016-05-25
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
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
RA00 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
23 March 2020