PH00027: AFTER MIGRATING TO WAS V9, THE CWSID0046E ERROR IS SEEN IN THE LOGS.

9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5

APAR status

• Closed as program error.

Error description

• There is a bug in the migration of messages from earlier WAS
  releases to V9.0.0.   The effect is that incorrect values of
  JMS delivery delay might occasionally be introduced.  This can
  lead to errors in the logs like CWSID0046E.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of the   *
  *                  default JMS Provider (SIB)                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: After migrating to WebSphere            *
  *                      Application Server Version 9 a          *
  *                      messaging engine fails and message      *
  *                      CWSID0046E is seen in the logs          *
  ****************************************************************
  * RECOMMENDATION:  Apply the APAR fix before attempting        *
  *                  to run the application server at version    *
  *                  9.                                          *
  ****************************************************************
  If the product is migrated to version 9 from a previous
  version and the Default JMS Provider (SIB) contains messages
  generated by the earlier version then incorrect values of
  JMS delivery delay might be assigned to the messages.
  This may also result in SIB Messaging engines failing to
  initialize and the CWSID0046E message reported in the logs.
  

Problem conclusion

• If the fix is applied before the application server has been
  started post migration then the problem will not occur.
  
  If the application server has been started then spurious
  values may be assigned to pre-existing SIB messages.  In this
  case the fix will enable the SIB messaging engines to
  initialize even if there are messages with an invalid delivery
  delay stored within them.
  
  It is unlikely that there will be any cases where we cannot
  determine if the delivery delay is bad, in these cases there
  are two custom properties that can be used to control the
  behaviour:
  
  sib.msgstore.maximumAllowedDeliveryDelayInterval
  
  A message with delivery delayed by more than this number of
  milliseconds after appserver start is treated as suspicious
  The default behaviour is no message is treated as suspicious.
  
  For example,
  sib.msgstore.maximumAllowedDeliveryDelayInterval=10 would mean
  that any message found at startup with a delivery delay of
  more than 10 milliseconds, where it might have been produced
  prior to the ifix with no delivery delay set, will be treated
  as suspect and handled according to the second custom property
  as follows:
  
  sib.msgstore.maximumAllowedDeliveryDelayAction will determine
  how a message with a suspicious delivery delay is handled.
  
  The default value of this property is "warn". A value of
  "warn" will produce the following message:
  
  CWSIP0580W: A message with ID xxxxxx system message ID yyyyyy
  was found in destination dddddd with a delivery delay
  exceeding the limit set by the property
  sib.msgstore.maximumAllowedDeliveryDelayInterval,
  that action taken was 'aaaaaa'
  
  The administrative console could then be used to unlock the
  message.
  
  "unlock" will cause the message to be unlocked in addition to
  producing the warning message.
  
  "exception" will cause the message to be moved to the
  exception destination with a return code 906 in addition to
  producing the warning message.
  
  
  
  WebSphere Application Server fixpack 9.0.0.10 and WebSphere
  Application Server Liberty fixpack 18.0.0.4. 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

• R900 PSY

     UP