So I was unable to produce a JUnit test that causes this issue to occur.
My first attempt was to use the SocketProxy in the test package of activemq.
I had the broker,the consumer, and the producer all running in the same JVM.
The consumer was using the VM transport and the producer was connecting to
the SocketProxy which was connecting to the brokers openwire transport. I
had a task running every 120 seconds that would rotate calling pause and
goOn of the SocketProxy. This did not work so I tried close and reopen on
the SocketProxy and that as well did not work.
My second attempt was to use Runtime.getRuntime().exec("ifconfig eth1 up");
with the same setup from my first attempt, but without the SocketProxy. This
also failed to reproduce the issue.
My third attempt was to remove the producer from the same machine and put it
on another machine on the local network, but this also was unable to
reproduce the issue.
My final attempt was to use the same configuration as the 3rd attempt but
put the producer on a machine that's on a different network that requires
vpn access to my workstation. I was able to reproduce the consumers hanging
in this configuration. So I believe it might have to do something with
latency, but at this point I am not sure.
So I am going to upload my test files if anyone wants to try to reproduce
it.
Hub.java <http://activemq.2283324.n4.nabble.com/file/n4689862/Hub.java>
Sender.java
<http://activemq.2283324.n4.nabble.com/file/n4689862/Sender.java>
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Consumer-hanging-after-a-producer-fails-for-being-inactive-tp4689775p4689862.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
