APAR status
Closed as program error.
Error description
In some MQ configurations the code to detect the location of the qm.ini file does not work. This causes the following errors to be observed during startup: Looks like: Sep 27 17:39:43 ingra2 user:err|error IIB[9896386]: IBM Integration Bus v9006 (M99.ESB.MDM1_BRK.adp_mdmorg) [Thread 21333] (Msg 1/1) BIP2111E: Message broker internal error: diagnostic information 'Couldn't locate qm.ini'. These errors can be safely ignored if coordinated transactions are not enabled for JDBC or JMS.
Local fix
The XA listeners can be enabled by setting the following env vars prior to starting the broker: JDBC: MQSI_XA_JDBC_START_LISTENER JMS: MQSI_XA_JMS_START_LISTENER
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus version 10 or App Connect Enterprise version 11 using either JDBC connectivity or the JMS Nodes. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: <span style="background-color:rgb(255, 255, 255)">In some MQ configurations the code to detect the location of the </span><span style="background-color:rgb(255, 255, 255)">qm.ini file does not work. This causes the following errors to </span><span style="background-color:rgb(255, 255, 255)">be observed during startup: </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">Looks like: Sep 27 17:39:43 ingra2 user:err|error IIB[9896386]: </span><span style="background-color:rgb(255, 255, 255)">IBM Integration Bus v9006 (M99.ESB.MDM1_BRK.adp_mdmorg) [Thread</span> <span style="background-color:rgb(255, 255, 255)">21333] (Msg 1/1) BIP2111E: Message broker internal error: </span><span style="background-color:rgb(255, 255, 255)">diagnostic information 'Couldn't locate qm.ini'. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">These errors can be safely ignored if coordinated transactions </span><span style="background-color:rgb(255, 255, 255)">are not enabled for JDBC or JMS. </span> 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 qm.ini is now correctly located in more scenarios preventing this error. Additionally the following environment variables have been introduced which allow the warning to be disabled: MQSI_XA_JDBC_STOP_LISTENER MQSI_XA_JMS_STOP_LISTENER When set to any non-null value prior to the startup of the Integration Node this causes the listener to be disabled without emitting a warning. Additionally the following env vars have been added which explicitly allow the listener to be started in the event tat the qm.ini file is not properly located and XA transactionality is required: <span style="background-color:rgb(255, 255, 255)">MQSI_XA_JDBC_START_LISTENER</span> <span style="background-color:rgb(255, 255, 255)">MQSI_XA_JMS</span><span style="background-color:rgb(255, 255, 255)">_START_LISTENER</span> --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.20 v11.0 11.0.0.8 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
IT17369
Reported component name
INTEGRATION BUS
Reported component ID
5724J0530
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-18
Closed date
2020-03-10
Last modified date
2020-03-10
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
5724J0530
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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 March 2020