Sorry Tim, I don't know how to reproduce this issue.
After this issue happened, I restarted AMQ broker by deleting the whole data
directory. I have been observing AMQ logs, but haven't found this issue
again.
Another point to note : Our app will try to subscribe again if subscription
fails for a
A packet capture on the machines indicates a perfectly valid
sequence of exchanges between the JMS publisher and the
consumer with the broker when the test is succeeding.
I'll run another test when it is in a failure mode to see what
is changing.
Jim
And this discussion may imply that perhaps the issue is with the client is
not being torn down properly from ActiveMQ's pov, but my webconsole always
shows zero producers and zero consumers once the test plugin has completed
its cycle.
https://github.com/apache/activemq-artemis/pull/208#issuecomme
Interesting:
https://github.com/chirino/stomp-benchmark/issues/11
On Wed, Apr 20, 2016 at 10:54 AM James A. Robinson
wrote:
> I can't immediately tell if this is a problem with the stomp client or
> with activemq, but I suspect the latter given what I was seeing. A
> monitor I put together to