I'm not sure if this is related or not, but the broker network is acting strangely with regard to holding on to messages instead of delivering them. I can enqueue a message which does not get delivered to the waiting & connected consumers. However, if I shut down one of the two brokers, often the message will immediately be delivered by the remaining broker.
eta wrote: > > This is from a queue consumer. I believe my client AMQ libraries are in > sync with the server. I see frequent failover messages even though > neither broker in the network has been restarted. > > 2007-07-31 04:24:28,124 [ActiveMQ Task] INFO > org.apache.activemq.transport.failover.FailoverTransport - Successfully > reconnected to tcp://broker2:61616 > 2007-07-31 04:25:58,928 [ActiveMQ Transport: > tcp://broker2/192.168.5.25:61616] WARN > org.apache.activemq.transport.failover.FailoverTransport - Transport > failed, attempting to automatically reconnect due to: java.io.IOException: > Unknown data type: -121 > java.io.IOException: Unknown data type: -121 > at > org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:344) > at > org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:275) > 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/Consumer-error-on-the-7-30-07-snapshot-tf4194847s2354.html#a11930332 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
