Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <48961809.1240391792779.JavaMail.jira@brutus>
Date: Wed, 22 Apr 2009 02:16:32 -0700 (PDT)
From: "Dejan Bosanac (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-2219) Admin console message.jsp references
 non-existant messageQuery.JMSMessageID field
In-Reply-To: <1070697259.1240370792281.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac resolved AMQ-2219.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0
         Assignee: Dejan Bosanac

Applied in SVN revision 767423. Thanks

> Admin console message.jsp references non-existant messageQuery.JMSMessageID field
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-2219
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2219
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: Windows XP
>            Reporter: Jeremy Grodberg
>            Assignee: Dejan Bosanac
>            Priority: Minor
>             Fix For: 5.3.0
>
>
> The Admin console/webapp can display a list of messages pending in a queue.  When you click on the link provided for one of the messages, the message details are shown.  That is, unless the message is no longer pending, at which point the Admin console throws an exception:
> {noformat}
> javax.el.PropertyNotFoundException: The class 'org.apache.activemq.web.MessageQuery' does not have the property 'JMSMessageID'.
>         at javax.el.BeanELResolver.getBeanProperty(BeanELResolver.java:547)
>         at javax.el.BeanELResolver.getValue(BeanELResolver.java:249)
>         at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:143)
>         at com.sun.el.parser.AstValue.getValue(AstValue.java:138)
>         at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:206)
>         at org.apache.jasper.runtime.PageContextImpl.evaluateExpression(PageContextImpl.java:984)
>         at org.apache.jsp.message_jsp._jspx_meth_c_when_0(org.apache.jsp.message_jsp:189)
>         at org.apache.jsp.message_jsp._jspx_meth_c_choose_0(org.apache.jsp.message_jsp:153)
>         at org.apache.jsp.message_jsp._jspService(org.apache.jsp.message_jsp:99)
>         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:93)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> etc...
> {noformat}
> The culprit is line 29 of message.jsp, which is
> {code:title=message.jsp}
> No message could be found for ID ${requestContext.messageQuery.JMSMessageID}
> {code}
> This should instead be 
> {code:title=message.jsp}
> No message could be found for ID ${requestContext.messageQuery.id}
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.