8 Replies Latest reply on Apr 17, 2009 9:14 PM by dave.stubbs

Serialisation errors in ActiveMQ.DLQ

dave.stubbs Mar 9, 2009 5:14 PM

I've started to get serialisation errors. Messages get written to the ActiveMQ.DLQ queue and when I click to view them I get the following errors....

javax.el.ELException: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.IOException: com.myclass

at javax.el.BeanELResolver.getValue(BeanELResolver.java:298)

at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:175)

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:1001)

at org.apache.jsp.message_jsp._jspx_meth_c_out_0(org.apache.jsp.message_jsp:489)

at org.apache.jsp.message_jsp._jspx_meth_c_otherwise_0(org.apache.jsp.message_jsp:345)

at org.apache.jsp.message_jsp._jspx_meth_c_choose_0(org.apache.jsp.message_jsp:160)

at org.apache.jsp.message_jsp._jspService(org.apache.jsp.message_jsp:101)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)

at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)

at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)

at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1124)

at org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)

at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)

at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:43)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)

at org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:81)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)

at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)

at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)

at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)

at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)

at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)

at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)

at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)

at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

at org.mortbay.jetty.Server.handle(Server.java:324)

at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)

at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)

at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)

at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)

at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)

at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)

at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)

Caused by: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.IOException: com.myclass

at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35)

at org.apache.activemq.command.ActiveMQObjectMessage.getObject(ActiveMQObjectMessage.java:183)

at org.apache.activemq.web.MessageQuery.getBody(MessageQuery.java:81)

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 javax.el.BeanELResolver.getValue(BeanELResolver.java:293)

... 41 more

Caused by: java.io.IOException: com.myclass

at org.apache.activemq.command.ActiveMQObjectMessage.getObject(ActiveMQObjectMessage.java:179)

... 47 more

Not quite sure what is wrong. The messages work 99% of the time but this is proving to be unreliable.

I never had this problem before with 5.1, but this has started now on 5.3 so I'm assuming a bug has been introduced.

1. Re: Serialisation errors in ActiveMQ.DLQ

davestanley Mar 9, 2009 6:26 PM (in response to dave.stubbs)

Hi Dave,
Are you using a 5.3 client jar?

Thanks
/Dave
Actions
2. Re: Serialisation errors in ActiveMQ.DLQ

mielket Mar 10, 2009 10:52 AM (in response to dave.stubbs)

Do you use the web console to access to message?
Actions
3. Re: Serialisation errors in ActiveMQ.DLQ

mielket Mar 10, 2009 12:14 PM (in response to dave.stubbs)

I think I know what's going on. Assuming you use the ActiveMQ web console to access and display messages on the queue. If a Message is of type javax.jms.ObjectMessage and perhaps also any other binary message format, you won't be able to view the message content in the web console. Instead the exception you see gets thrown. The reason for this is that the message parsing routine does not know how to build the message from the object serialized format. My suspicion is that is even fails to load the class com.myclass.
I agree the admin console could catch this error and at least display the message properties but don't parse the message body.
Actions
4. Re: Serialisation errors in ActiveMQ.DLQ

mielket Mar 12, 2009 4:57 AM (in response to mielket)

Btw, I have raised AMQ-2154 at Apache.
Actions
5. Re: Serialisation errors in ActiveMQ.DLQ

dave.stubbs Mar 18, 2009 2:25 PM (in response to mielket)

Why do these messages end up in the DLQ in the first place. I never used to see this happening when I used 5.1 & 5.2 of MQ, it's only since moving to 5.3 that I started getting these.
Actions
6. Re: Serialisation errors in ActiveMQ.DLQ

mielket Mar 19, 2009 5:22 AM (in response to dave.stubbs)

Messages that cannot be delivered will eventually be sent to a dead letter queue. Have a look at
http://activemq.apache.org/message-redelivery-and-dlq-handling.html for more information.

I don't think this behavior has changed between 5.1|5.2 and 5.3.
Actions
7. Re: Serialisation errors in ActiveMQ.DLQ

kernow Apr 9, 2009 7:03 AM (in response to mielket)

The exception being displayed is certainly caused by not being able to 'view' the message. My understanding is that the web console simply tries to 'toString()' the message - consequently if the message contains a class not on its class path you will get the error.

Try copying the jars that contain the classes in the message to the admin webapp and then try viewing them again.

This will not solve why the messages ended up on the DLQ - you'll need to look at your application to see why it couldn't process them.
Actions
8. Re: Serialisation errors in ActiveMQ.DLQ

dave.stubbs Apr 17, 2009 9:14 PM (in response to dave.stubbs)

Will retest when bug fixed version released.
Actions

Go to original post