thread dumps of the brokers may help, for some reason a topic send is blocking when being forwarded, and there is no discarding, so there is an eventual push back on the producer. A thread dump of the receiving broker, Broker A, may point to what it is doing.
On 17 January 2014 22:03, oholiab <[email protected]> wrote: > Sorry, forgot to add logfile stuff... > > These hangups are often accompanied or preceded by log entries like: > > 2014-01-16 17:45:02,816 | WARN | TopicSubscription: > consumer=B->A-35971-1389919240382-4:3:1:1, destinations=23, dispatched=1000, > delivered=0, matched=1001, discarded=0: has twice its prefetch limit > pending, without an ack; it appears to be slow | > org.apache.activemq.broker.region.TopicSubscription | ActiveMQ NIO Worker 94 > > But the network connectors always continue to appear open in jconsole > > I'm suspecting this has something to do with the buffers filling up and not > having space for an ack to be sent before the message can be consumed but > it's only a theory > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/TCP-send-and-receive-buffers-filling-preventing-openwire-communication-tp4676493p4676495.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
