PM27496: SORTING QUEUES BY QUEUE DEPTH PRODUCES INCORRECT SORT RESULT. QUEUE DEPTHS REMAIN IN APPARENT RANDOM ORDER.

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• In the WebSphere Application Server administrative console you
  can list the queue points for a messaging engine under "Service
  Integration: Buses > Bus_Name > Messaging Engines > ME_Name >
  Queue Points".  If you sort the list on "Queue Depth", the
  console displays the queue points in the wrong order.  Rather
  than performing a numeric sort (e.g. 0, 7, 33, 500, 1500) it
  performs a string sort (e.g. 0, 1500, 33, 500, 7).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the default messaging provider for *
  *                  IBM WebSphere Application Server            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Sorting by queue depth produces the     *
  *                      incorrect result.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem was that the sort treated the depth as a String
  and was therefore ordered alphabetically.    As a result 2
  > 10, so the order was incorrect.
  

Problem conclusion

• The fix is to sort the list by treating depth as a numeric
  value, resulting in the expected sort.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 7.0.0.17.  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

  PLAT MSG COM

• Fixed component ID

  620800101

Applicable component levels

• R300 PSY

     UP