Thanks, Jim. I neglected to add that we are using the failover URI in
production. The main problem seems to be around surviving debugging. For
instance, I someone is debugging a service, and goes away for a cup of
coffee for a few minutes, they will invariably find that the broker has send
an NMSEx
I have a dump resulting from a heap corruption when calling
ActiveMQConsumer::~ActiveMQConsumer(). I wanted to ask you folks for any
advice before I dig too far. Scanned through Jira but didn't find anything
current and pertinent. I'm fairly new to ActiveMQ and the people who wrote the
origi
And alternatively, is the broker(s) to which that URI connects up and
healthy? Is there any relevant info in its/their logs?
On Oct 10, 2016 7:25 AM, "Tim Bain" wrote:
> What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your process? Is
> it a valid URI? Could something be wrong with t
What's the value of ${JMS_X_SITE_CSV_URL} at runtime for your process? Is
it a valid URI? Could something be wrong with that variable?
On Oct 10, 2016 2:49 AM, "divinedragon" wrote:
> Ok. So, removing the does get rid of the WARN entry.
> But, then I don't want to remove it. What is the confi
Ok. So, removing the does get rid of the WARN entry.
But, then I don't want to remove it. What is the configuration issue with
the ???
On Mon, Oct 10, 2016 at 12:16 PM, Tim Bain [via ActiveMQ] <
ml-node+s2283324n4717710...@n4.nabble.com> wrote:
> Does the behavior change if you comment out your
