activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Mielke (JIRA)" <>
Subject [jira] Commented: (AMQ-2154) trying to access an ObjectMessage in the AMQ web console results in com.myclass...
Date Thu, 12 Mar 2009 11:02:40 GMT


Torsten Mielke commented on AMQ-2154:

I fully agree with your points Giovani. However I don't think it should be a requirement to
add application level classes to the brokers classpath in order to drill into individual messages.
I can live with the fact that the message content cannot be displayed but it should not generate
a fully blown up error with stack trace in the html page but some meaningful response. After
all, the message properties can still be displayed. Hence my motivation for a fix. 

> trying to access an ObjectMessage in the AMQ web console results in
> -------------------------------------------------------------------------------------------------------
>                 Key: AMQ-2154
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.1.0
>         Environment: web console, ObjectMessage
>            Reporter: Torsten Mielke
>            Priority: Minor
>         Attachments: AMQ-2154.patch
> The web console can be used to drill into individual message and display both their properties
as well as payload. 
> Displaying the payload generally works fine for TextMessages, etc but fails for ObjectMessages
and probably other binary payload formats.
> This is okay and kind of expected but rather than throwing an exception with a large
stack trace back to the browser client, we should capture the ex and display at least the
message properties and also a short message that the content cannot be displayed due to its
binary content.
> Error msg and stack trace that is thrown:
> {code}
> com.myclass
> 	at org.apache.activemq.command.ActiveMQObjectMessage.getObject(
> 	at org.apache.activemq.web.MessageQuery.getBody(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at javax.el.BeanELResolver.getValue(
> 	at javax.el.CompositeELResolver.getValue(
> 	at com.sun.el.parser.AstValue.getValue(
> 	at com.sun.el.ValueExpressionImpl.getValue(
> 	at org.apache.jasper.runtime.PageContextImpl.evaluateExpression(
> 	at org.apache.jsp.message_jsp._jspx_meth_c_out_0(org.apache.jsp.message_jsp:400)
> 	at org.apache.jsp.message_jsp._jspx_meth_c_otherwise_0(org.apache.jsp.message_jsp:334)
> 	at org.apache.jsp.message_jsp._jspx_meth_c_choose_0(org.apache.jsp.message_jsp:151)
> 	at org.apache.jsp.message_jsp._jspService(org.apache.jsp.message_jsp:92)
> 	at org.apache.jasper.runtime.HttpJspBase.service(
> 	at javax.servlet.http.HttpServlet.service(
> 	at org.apache.jasper.servlet.JspServletWrapper.service(
> 	at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> 	at org.apache.jasper.servlet.JspServlet.service(
> 	at javax.servlet.http.HttpServlet.service(
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
> 	at org.springframework.web.filter.RequestContextFilter.doFilterInternal(
> 	at org.springframework.web.filter.OncePerRequestFilter.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
> 	at org.apache.activemq.web.SessionFilter.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
> 	at org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
> 	at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
> 	at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(
> 	at
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(
> 	at org.mortbay.jetty.handler.ContextHandler.handle(
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(
> 	at org.mortbay.jetty.Server.handle(
> 	at org.mortbay.jetty.HttpConnection.handleRequest(
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
> 	at org.mortbay.jetty.HttpParser.parseNext(
> 	at org.mortbay.jetty.HttpParser.parseAvailable(
> 	at org.mortbay.jetty.HttpConnection.handle(
> 	at
> 	at org.mortbay.thread.BoundedThreadPool$
> {code}

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

View raw message