Yep, if getObject() throws an exception, that explains what you're seeing, so now it's just a matter of figuring out what's causing the exception. I'd check that there is only one copy of your class on the classpath, and that it's the same class definition on both the producer and the consumer. getObject() is a great place for your breakpoint, BTW. On Feb 11, 2016 11:51 PM, "mhemple" <mhem...@gmail.com> wrote:
> Tim, I really appreciate the help. > > Yes there are no serialization errors (or DEBUGS) in the AMQ log. I wrote > a > java app to intercept messages from the queue. The message object is not > deserializing (message.getObject() is throwing an error) so I still think > this is the right track. > > In JConsole, when a message is published, I do see the enqueue count > increase by 1. Shortly thereafter the dequeue and dispatch counts both > increase by 1. > > I haven't gotten around to it, but I'll set a breakpoint in > ActiveMQObjectMessage tomorrow to see whats going on there. > > Thanks. > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Messages-dequeued-but-not-consumed-tp4707380p4707442.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
