I don't know the HornetQ code to know if there are differences (maybe someone from the Artemis side knows the answer), though I'd expect them to be very similar.
That does sound like serialization is part of the problem, though I'd expect to see errors (or at least DEBUGs, if you change the Log4J level to enable them) in the logs in that case. Does the fact that you've never mentioned any log lines mean there aren't any? When you look at the queue in JConsole and a single message is published, you should see the enqueue count increase and also one of the other counts increase. Does that happen, and if so which count is it? In your first post you asked about where to put a breakpoint. It's been a while since I stepped through the deserialization code so I don't remember offhand, but you should be able to find it quickly by searching for references to ActiveMQObjectMessage. Sorry I can't be more help than that at the moment. Tim Yes we are using ActiveMQObjectMessages. ActiveMQTextMessages are working for our other queues. I would love to serialize to text but, unfortunately that isn't an option at this point. We're using object messages with Hornet without issue. Are there major differences between object messages from the two brokers? I don't think we're doing anything that would cause deserialization on the broker. I added our jar to the AMQ classpath just in case, but the problem persists. -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-dequeued-but-not-consumed-tp4707380p4707430.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
