PK89856: WMQ JMS DESTINATION MESSAGE EXPIRY SPECIFIED IN THE ADMINISTRATIVE CONSOLE DOES NOT HAVE THE DESIRED EFFECT

Fixes are available

APAR status

Closed as program error.

Error description

IBM WebSphere MQ Queue destinations defined in the
WebSphere AppServer Administrative Console do not
honor message expiry set under 'Advanced Properties' for the JMS
Queue Destinations.  Even if an expiration value is set, the
messages never expire.  If the Priority value type is
SPECIFIED, then a specified Expiry value will be
honored.
.
   Also, there is a problem processing the attributes which can
result in the following error message.
[6/7/10 15:57:26:821 EDT] 00000023 ResourceMgrIm E   WSVR0017E:
Error encountered binding the J2EE resource,
Reeceive_Q, as jms/Reeceive_Q from
/opt/WebSphere/70/ESB/profiles/AppSrv01/config/cells/CELL_NAME/
nodes/NODE_NAME/servers/server1/resources.xml
java.lang.IllegalStateException: QUEUE_DEFINED
 at com.ibm.ws.runtime.component.binder.MQQueueBinder.
getBindingObject(MQQueueBinder.java:179)
 at com.ibm.ws.runtime.component.ResourceMgrImpl.bind
(ResourceMgrImpl.java:501)
 at com.ibm.ws.runtime.component.ResourceMgrImpl.
installResourceProvider(ResourceMgrImpl.java:1537)
 at com.ibm.ws.runtime.component.ResourceMgrImpl.
installResource(ResourceMgrImpl.java:1370)
 at com.ibm.ws.runtime.component.ResourceMgrImpl.
installResources(ResourceMgrImpl.java:1311)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Version 7.0 using WebSphere MQ as a         *
*                  messaging provider                          *
****************************************************************
* PROBLEM DESCRIPTION: Specifying an Expiry value for a        *
*                      WebSphere MQ JMS destination has no     *
*                      effect.  The value is ignored.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
While binding the JMS destination into the JNDI namespace
the value type of the Priority property was incorrectly read
from the configuration when determining the value type of the
Expiry property.
As a result, any value specified as the Expiry was ignored,
unless the Priority value type was SPECIFIED.
Otherwise the Priority value type is used for the Expiry.

Problem conclusion

The fix for this APAR corrects the code that binds the
WebSphere MQ JMS destination into the JNDI namespace, so that
the value type of Expiry property is read correctly.

The fix for this APAR is currently targeted for inclusion in
fix pack 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
PK89856
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-25
Closed date
2009-07-30
Last modified date
2010-06-09

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PK91368 PM09779 PM09780

Fix information

Fixed component name
PLAT MSG COM
Fixed component ID
620800101

Applicable component levels

R300 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK89856: WMQ JMS DESTINATION MESSAGE EXPIRY SPECIFIED IN THE ADMINISTRATIVE CONSOLE DOES NOT HAVE THE DESIRED EFFECT

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

R300 PSY

Document Information

Share your feedback

Need support?