IT40641: MQTT CLIENT ID USED IN EVENT PUBLICATION IS NOT UNIQUE BETWEEN EVENT TYPES

APAR status

• Closed as program error.

Error description

• When Admin Events, Business Events, or Operation Events are
  configured to be published over MQTT the same client ID will be
  used for all three types of message. Each event type uses a
  separate MQTT connection and so causes the clients to keep
  disconnecting each other when they are configured to talk to the
  same MQTT broker. The client ID must be unique for all
  connections so when a message of one event type gets published
  it disconnects the clients of the other types. This can lead to
  missed publication of messages if two threads try to publish two
  messages of different types at the same time.
  
  Additionally the Client ID property on the MQTTPublish property
  is ignored even if it is configured to a valid value. All event
  publications from the same integration server will use the same
  client ID regardless of what policies are specified.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of monitoring events in IBM App Connect Enterprise
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  <div><div><span style="color:#000000">When Admin Events,
  Business Events, or Operation Events are configured to be
  published over MQTT the same client ID will be used for all
  three types of message. Each event type uses a separate MQTT
  connection and so causes the clients to keep disconnecting each
  other when they are configured to talk to the same MQTT broker.
  The client ID must be unique for all connections so when a
  message of one event type gets published it disconnects the
  clients of the other types. This can lead to missed publication
  of messages if two threads try to publish two messages of
  different types at the same time.</span></div> <div><span
  style="color:#000000">Additionally the Client ID property on the
  MQTTPublish property is ignored even if it is configured to a
  valid value. All event publications from the same integration
  server will use the same client ID regardless of what policies
  are specified.</span></div></div>
  

Problem conclusion

• The product now respects the Client ID property on the
  MQTTPublish policy if specified, and will otherwise use a
  different client ID for all three types of events.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.19
  v12.0      12.0.5.0
  
  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 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