You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (Commented) (JIRA)" <ji...@apache.org> on 2011/11/17 19:19:51 UTC
[jira] [Commented] (QPID-3617) AMQQueueMBean.viewMessages: Viewing
message without priority set ends with NullPointerException
[ https://issues.apache.org/jira/browse/QPID-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152183#comment-13152183 ]
Justin Ross commented on QPID-3617:
-----------------------------------
Reviewed by Robbie. Approved for 0.14.
> AMQQueueMBean.viewMessages: Viewing message without priority set ends with NullPointerException
> -----------------------------------------------------------------------------------------------
>
> Key: QPID-3617
> URL: https://issues.apache.org/jira/browse/QPID-3617
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Management : JMX Interface, Python Client
> Affects Versions: 0.10, 0.12, 0.13, 0.14, 0.15
> Reporter: Keith Wall
> Assignee: Robbie Gemmell
> Fix For: 0.15
>
>
> If a user of the JMX Console (or Management Console) tries to view a message without message priority (such as those sent by the Python Client) the user sees a NullPointerException.
> The issue is with the defaulting logic in MessageTransferHeader#getPriority().
> {code}
> 2011-11-15 12:19:34,154 ERROR [RMI TCP Connection(2)-169.24.25.106] (AMQQueueMBean.java:506) - error
> java.lang.NullPointerException
> at org.apache.qpid.server.message.MessageTransferHeader.getPriority(MessageTransferHeader.java:85)
> at org.apache.qpid.server.queue.AMQQueueMBean.getMessageTransferMessageHeaderProps(AMQQueueMBean.java:568)
> at org.apache.qpid.server.queue.AMQQueueMBean.viewMessages(AMQQueueMBean.java:482)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
> at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
> at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
> at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
> at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
> at javax.management.StandardMBean.invoke(StandardMBean.java:391)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
> at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
> at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
> at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
> at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360)
> at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
> at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
> at sun.rmi.transport.Transport$1.run(Transport.java:159)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org