PK95559: MESSAGE EXPIRATION IS NOT HONORED FOR A MESSAGE SENT FROM WEBSPHERE MQ TO THE SERVICE INTEGRATION BUS

Fixes are available

APAR status

Closed as program error.

Error description

An attempt to set the message exipration on a request message
from WebSphere MQ is not being propogated back in the response
message from the Service Integration Bus in WebSphere 6.1.
The message originating from WebSphere MQ destined to the Bus
could be over a WMQ Link, WMQ Client Link or via a WMQ Server
member of the Bus.
Per our documentation if there is no JMSExpiration field set
in the MQRFH2 of the message, the value of the the MQMD Expiry
field should be used to build the JMSExpiration value.  This
is not being calculated correctly.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server 6.1    *
*                  and 7.0 receiving messages from WebSphere   *
*                  MQ over a WebSphere MQ link, or from a      *
*                  WebSphere MQ Server member of the bus       *
****************************************************************
* PROBLEM DESCRIPTION: Messages sent by non-JMS WebSphere      *
*                      MQ applications have an incorrect       *
*                      JMSExpiration value when they arrive    *
*                      in the bus                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Messages arriving in a bus from non-JMS WebSphere MQ clients
have an incorrect JMSExpiration value.
This expiration value is taken directly from the MQMD, rather
than being translated into a timestamp for when the message
should expire.

The incorrect JMSExpiration header means that the messages
never expire.

Problem conclusion

The default messaging provider now correctly converts the MQMD
expiration, which is represented as the number of centiseconds
until expiration, into a proper JMS expiration. The JMS
expiration is the timestamp when the JMS message should expire.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.29 and 7.0.0.9.  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 number
PK95559
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-07
Closed date
2009-09-25
Last modified date
2009-09-25

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
620600101

Applicable component levels

R200 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK95559: MESSAGE EXPIRATION IS NOT HONORED FOR A MESSAGE SENT FROM WEBSPHERE MQ TO THE SERVICE INTEGRATION BUS

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R200 PSY

Document Information

Share your feedback

Need support?