activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <>
Subject Re: NullPointerException in AbstractInactivityMonitor
Date Fri, 07 Dec 2012 18:59:52 GMT
On Fri, 2012-12-07 at 09:28 -0800, mleiseca wrote: 
> ceposta wrote
> > Looks like the content of the message is null and it cannot be marshalled.
> > Not sure why there would be null messages... are producers sending them?
> That shouldn't be happening for a couple of reasons:
>  - we are using spring to send messages and there are only a couple of
> places where this code is called. It doesn't look like there is any way that
> a producer could be sending a null message
>  - I should have mentioned this in the initial post, but most messages are
> actually sent to a broker embedded in each tomcat app and then forwarded on
> to a central broker. If we were doing something like trying to send a null
> message, I would expect to see some errors in the embedded broker logs
> instead of the central broker log.

Have you tried setting concurrentStoreAndDispatchQueues=false to see if
it has any effect?  

> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

Tim Bish
Sr Software Engineer | RedHat Inc. | | 
skype: tabish121 | twitter: @tabish121

View raw message