Hi, I have been busy with other stuff so I have not been able to focus on this problem until now.
For now I have not been able to create a test case that could reproduce this problem. However I have continued my investigations. I once again made ActiveMQ log everything and found something that could perhaps tell a bit more about the issue at hand. I was looking at log entries created during successful communication and how things change when the communication stops. During successful communication I can see that the VMTransport thread in the Server broker logs a MessageAck in PrefetchSubscription.acknowledge and after that the ActiveMQ Transport thread in the Client broker logs a MessageAck with the same MessageId (again in PrefetchSubscription.acknowledge). However when the communication stalls I can see the Server broker still logging acknowledgements to some messages but the Client broker does not do that and at this point no more messages reach the Server broker from the Client broker (at least for that queue). The strange thing is, that I was able to make the communication going again by temporarily cutting the network connections between the Client and Server (I did this by disabling the Client machines network interface). I'll continue my investigation of this subject but at the same time hope that you could be able to perhaps come up with something based on my findings. Br, -Pauli Kaila -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-brokers-message-forwarding-between-brokers-stops-tp3060260p3090850.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
