IT32159: HIGH CPU AFTER A WEBSPHERE JMS CONNECTION ERROR

Fix packs for DataPower Gateway version 2018.4.1

APAR status

• Closed as program error.

Error description

• The user observes DataPower might face high CPU in case of
  continuous Websphere JMS connection errors.
  In particular, this was observed in a Strict-Message-Order
  usecase on a secondary instance that was blocked from accessing
  the target SI Bus JMS queue as expected.
  It seems some indefinite retry drives the high CPU.
  

Local fix

Problem summary

• For DataPower users who use WebSphere JMS and have enabled the
  "Strict Message Ordering" for the corresponding JMS
  Destinations, if there are more than two DataPower appliances
  trying to make subscriptions to the same JMS Destinations, then
  DataPower might be hanging on the retrying and cause high CPU
  usage issue. When the "Strict Message Ordering" is enabled in
  JMS server, it allows only one JMS client for one JMS
  Destination at the same time.
  

Problem conclusion

• Fix is available in 2018.4.1.11
  For a list of the latest fix packs available, please see:
  http://www-01.ibm.com/support/docview.wss?uid=swg21237631
  

Temporary fix

• Avoid setting more than one DPs to connect to one JMS
  Destination at the same time.
  

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

  DATAPOWER

• Fixed component ID

  DP1234567

Applicable component levels

• R18X PSY

     UP