PH05890: UNEXPECTED RESPONSE FROM WEBSPHERE APPLICATION SERVER TO DATAPOWER CLIENT REQUEST

8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When using DataPower to connect to WAS 8.5.5.3 JMS server (via
  XMS API), and both functions "Maintain strict message order"
  and "Blocked retry timeout in milliseconds" in server are
  enabled, the client side (DataPower) gets unexpected response
  from server side.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of the   *
  *                  default messaging provider (SIB) who        *
  *                  require strict message ordering.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Multiple consumers may be created       *
  *                      concurrently resulting in messages      *
  *                      being delivered out of order.           *
  ****************************************************************
  * RECOMMENDATION:  apply the apar fix if strict message        *
  *                  ordering is required.                       *
  ****************************************************************
  When multiple consumers are used to request messages there
  is a possibility, in complex scenarions, that two concurrent
  consumers may be created depsite strict message ordering
  having been specified.  This can occur when the implementation
  erroneously allows a new consumer to be created despite the
  presence of a message locked under a transaction by an existing
  consumer.  This can result in out of order delivery.
  

Problem conclusion

• The implementation was modified so that multiple consumers
  will not be created concurrently when using strict message
  ordering.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.5.5.15 and 9.0.0.11.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP