APAR status
Closed as program error.
Error description
Additional Symptom(s) Search Keyword(s):Application Message Flows with SOAP nodes that are configured to use a multipart WSDL, WSDL file contains imports to other WSDL file, with the WSDL files stored directly within an Application can fail to start with an error of the following form:- BIP3726E: com.ibm.broker.axis2.MbSoapException: Failed to setup Axis2 Caused by: BIP3732E: com.ibm.broker.axis2.MbSoapException: Could not find the specified binding information in the supplied WSDL file. BIP3732E: The specified WSDL binding 'name' could not be found in the supplied WSDL file 'name'.wsdl. The WSDL binding P_CheckBinding from the target namespace 'namespace' associated with message set '' was not found in the WSDL file 'name'.wsdl. This could be because the WSDL file is missing, invalid or corrupt.Application Message Flows with SOAP nodes that are configured to use a multipart WSDL, WSDL file contains imports to other WSDL file, with the WSDL files stored directly within an Application can fail to start with an error of the following form:- BIP3726E: com.ibm.broker.axis2.MbSoapException: Failed to setup Axis2 Caused by: BIP3732E: com.ibm.broker.axis2.MbSoapException: Could not find the specified binding information in the supplied WSDL file. BIP3732E: The specified WSDL binding 'name' could not be found in the supplied WSDL file 'name'.wsdl. The WSDL binding P_CheckBinding from the target namespace 'namespace' associated with message set '' was not found in the WSDL file 'name'.wsdl. This could be because the WSDL file is missing, invalid or corrupt.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM App Connect Enterprise V11. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Application message flows with SOAP nodes that are configured to use a multipart WSDL, where the WSDL file contains imports to other WSDL files and the WSDL files are stored directly within an Application can fail to start with an error of the following form:- BIP3726E: com.ibm.broker.axis2.MbSoapException: Failed to setup Axis2 Caused by: BIP3732E: com.ibm.broker.axis2.MbSoapException: Could not find the specified binding information in the supplied WSDL file. BIP3732E: The specified WSDL binding 'name' could not be found in the supplied WSDL file 'name'.wsdl. The WSDL binding P_CheckBinding from the target namespace 'namespace' associated with message set '' was not found in the WSDL file 'name'.wsdl. This could be because the WSDL file is missing, invalid or corrupt.
Problem conclusion
Message flows no longer fail to start with an exception when configured to use a multipart WSDL where the WSDL file contains imports to other WSDL files and the WSDL files are stored directly within an Application. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v11.0 11.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
IT29332
Reported component name
APP CONNECT ENT
Reported component ID
5724J0550
Reported release
B00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-06-04
Closed date
2020-02-20
Last modified date
2020-02-20
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
APP CONNECT ENT
Fixed component ID
5724J0550
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
20 February 2020