I am using AMQ 4.1.0 and I got the same stack trace. This resulted in a single message dropped.
Exception in thread "ActiveMQ Transport: tcp:///10.10.100.183:1534" java.lang.ArrayIndexOutOfBoundsException: 1802 at org.apache.activemq.openwire.OpenWireFormat.getFromUnmarshallCache(OpenWireFormat.java:513) at org.apache.activemq.openwire.v2.BaseDataStreamMarshaller.tightUnmarsalCachedObject(BaseDataStreamMarshaller.java:137) at org.apache.activemq.openwire.v2.ConsumerInfoMarshaller.tightUnmarshal(ConsumerInfoMarshaller.java:69) at org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:347) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:273) at org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136) at java.lang.Thread.run(Thread.java:619) -- View this message in context: http://www.nabble.com/Servicemix-Camel-problem---ToJbiProcessor-hangs-tp18651622s22882p18719253.html Sent from the Camel - Users mailing list archive at Nabble.com.
