What message type are you using? Only ActiveMQObjectMessages ( http://activemq.apache.org/maven/apidocs/org/apache/activemq/command/ActiveMQObjectMessage.html) would use serialization, so if that's what you're using then try sending an ActiveMQTextMessage instead and see if it makes it through.
Also, is there any possibility that you're doing something on the broker that would cause a deserialization to be done (embedded Camel routes, queue browsing, that sort of thing), and if so, is a JAR containing your class on the broker's classpath? I personally would always serialize to text (XML/JSON/protobuffs/etc.) and send ActiveMQTextMessages rather than using ActiveMQObjectMessages and relying on Java's crappy built-in serialization support and opening myself up to the kinds of deployment/classpath issues that come with using ActiveMQObjectMessages. ActiveMQTextMessages are a small amount more work but they're less magical and you can better predict whether your implementation will work correctly. Tim On Feb 11, 2016 10:32 AM, "mhemple" <mhem...@gmail.com> wrote: > Thanks. The messages are not expiring. I believe they are being dequeued > by > spring integration but never making it to my consumer. Do you think it > could be a serialization issue? > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Messages-dequeued-but-not-consumed-tp4707380p4707425.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
