MSGS0509E: The JMS Server security service was unable to authorize userid xxxxxx to access resource SYSTEM.DEAD.LETTER.QUEUE with admin permission
 Technote (troubleshooting)
 
Problem(Abstract)
Using the IBM® WebSphere® Application Server V5.0 (all releases) Embedded Java™ Message Service (JMS) Server, when a message is sent to the SYSTEM.DEAD.LETTER.QUEUE, the following exception may be thrown:

MSGS0509E: The JMS Server security service was unable to authorize userid sxxxxxxx to access resource SYSTEM.DEAD.LETTER.QUEUE with admin permission

and followed by exceptions:

WMSG0018E: and MQJMS1081: message requeue failed
 
Cause
Code defect in Embedded JMS
 
Resolving the problem
Example of the stack trace:


[9/5/03 9:48:44:966 CDT] 3c847bfe JMSSecuritySe E MSGS0509E: The JMS Server security service was unable to authorize userid
xxxxxx to access resource
SYSTEM.DEAD.LETTER.QUEUE with admin permission
[9/5/03 9:48:45:068 CDT] 8e9bbd6 JMSExceptionL E WMSG0018E: Error
on JMSConnection for MDB xxxxxx/PostDCMInteractionRequestMDB ,
JMSDestination topic/xxxxxx/DeploymentEngine/HighLevelOutput:
javax.jms.JMSException: MQJMS1081: Message requeue failed
at
com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:535)
at
com.ibm.mq.jms.MQQueueAgentThread.backoutRequeue(MQQueueAgentThread.java:1021)
at
com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java:374)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1568) at java.lang.Thread.run(Thread.java:513)
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2035
at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java(Compiled Code))
at com.ibm.mq.jms.MQQueueAgentThread.put1WithContext(MQQueueAgentThread.java:1428)
at com.ibm.mq.jms.MQQueueAgentThread.backoutRequeue(MQQueueAgentThread.java:995)
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThreadjava:374)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1568)at java.lang.Thread.run(Thread.java:513)

Resolve the problem by modifying the XML file <WSAS_HOME>\config\cells\cell_name\integral-jms-authorizations.xml
(where <WSAS_HOME> is the directory where WebSphere Application Server is installed).

This information is documented in the WebSphere Application Server Information Center. To find the appropriate section,

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1138576
IBM Group: Software Group
Modified date: May 21, 2008