APAR status
Closed as program error.
Error description
If an Integration API application attempts to connect to multiple remote brokers over SSL and if one of the connection fails due to incorrect ssl settings then all the subsequent connection creation will also fail. For example, if the .broker file has an incorrect password for the truststore then the remote connection will fail with following exception as expected. com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: Keystore was tampered with, or password was incorrect at com.ibm.broker.config.proxy.WebSocketSender.connect(WebSocketSen der.java:321) at com.ibm.broker.config.proxy.WebSocketSender.send(WebSocketSender .java:185) at com.ibm.broker.config.proxy.SendManager.send(SendManager.java:17 0) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerWithB roker(AdministeredObjectPool.java:2198) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:2013) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:1920) at com.ibm.broker.config.proxy.BrokerProxy.<init>(BrokerProxy.java: 450) at com.ibm.broker.config.proxy.BrokerProxy.getInstance(BrokerProxy. java:1056) But subsequent connections to other remote brokers with correct .broker file settings will also fail with following exception. com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: WebSocketClient@374732002 is not started at com.ibm.broker.config.proxy.WebSocketSender.connect(WebSocketSen der.java:321) at com.ibm.broker.config.proxy.WebSocketSender.send(WebSocketSender .java:185) at com.ibm.broker.config.proxy.SendManager.send(SendManager.java:17 0) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerWithB roker(AdministeredObjectPool.java:2198) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:2013) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:1920) at com.ibm.broker.config.proxy.BrokerProxy.<init>(BrokerProxy.java: 450) at com.ibm.broker.config.proxy.BrokerProxy.getInstance(BrokerProxy. java:1056)
Local fix
n/a
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V10.0 using integration API applications with SSL. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: If an Integration API application attempts to connect to multiple remote brokers over SSL and if one of the connection fails due to incorrect ssl settings then all the subsequent connection creation will also fail. For example, if the .broker file has an incorrect password for the truststore then the remote connection will fail with following exception as expected. com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: Keystore was tampered with, or password was incorrect at com.ibm.broker.config.proxy.WebSocketSender.connect(WebSocketSen der.java:321) at com.ibm.broker.config.proxy.WebSocketSender.send(WebSocketSender .java:185) at com.ibm.broker.config.proxy.SendManager.send(SendManager.java:17 0) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerWithB roker(AdministeredObjectPool.java:2198) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:2013) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:1920) at com.ibm.broker.config.proxy.BrokerProxy.<init>(BrokerProxy.java: 450) at com.ibm.broker.config.proxy.BrokerProxy.getInstance(BrokerProxy. java:1056) But subsequent connections to other remote brokers with correct .broker file settings will also fail with following exception. com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: WebSocketClient@374732002 is not started at com.ibm.broker.config.proxy.WebSocketSender.connect(WebSocketSen der.java:321) at com.ibm.broker.config.proxy.WebSocketSender.send(WebSocketSender .java:185) at com.ibm.broker.config.proxy.SendManager.send(SendManager.java:17 0) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerWithB roker(AdministeredObjectPool.java:2198) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:2013) at com.ibm.broker.config.proxy.AdministeredObjectPool.registerAdmin isteredObject(AdministeredObjectPool.java:1920) at com.ibm.broker.config.proxy.BrokerProxy.<init>(BrokerProxy.java: 450) at com.ibm.broker.config.proxy.BrokerProxy.getInstance(BrokerProxy. java:1056)
Problem conclusion
The product now correctly creates new remote broker connections from integration API applications. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.18 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
IT29161
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
2019-05-22
Closed date
2019-09-30
Last modified date
2019-10-01
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
[{"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:
01 October 2019