Using activemq version 5.7.0A component which had a durable subscription to a
VirtualTopic was undeployed. This component was then restarted and the
durable subscription was given a different client id. This is causing an
issue of storage since the previous subscription with the old client id is
st
Tim,
I'm using ActiveMQ-5.5.1 (yes I know there are newer versions,
but we're not ready to upgrade our production code just yet. We have a star
topology with multiple end point brokers feeding a central broker (hub) that
controls routing of messages from end point to end point.
I've observed it in practice, so I've never felt the need to search for a
unit test that shows the same thing, sorry. Luckily they're all open
source, so you can do that yourself if you're so inclined.
On Sep 17, 2015 7:09 AM, "bbuzzard" wrote:
> I assumed it worked that way, but I wasn't sure.
I assumed it worked that way, but I wasn't sure. Thank you.
Is there a specific Test Case that proves this?
From: Tim Bain [via ActiveMQ] [mailto:ml-node+s2283324n4702052...@n4.nabble.com]
Sent: Wednesday, September 16, 2015 11:04 PM
To: Billy Buzzard
Subject: Re: Does Publisher Flow Control wor
