I don't have the ability right now to read the FailoverTransport source
> code to find out. Though of course you could if you have time.
>
> Tim
> On Jun 17, 2016 5:29 PM, "arkin" wrote:
>
> In the following example from
> http://activemq.apache.org/failover-transp
l2 or is the choice between the two
local urls random?
Once a connection to local2 is established, the client will not attempt to
connect to local1 unless the connection to local2 is disrupted. Is that
correct?
Thanks,
- Arkin
--
View this message in context:
http://activemq.22
r is the choice between the two
local urls random?
Once a connection to local2 is established, the client will not attempt to
connect to local1 unless the connection to local2 is disrupted. Is that
correct?
Thanks,
- Arkin
I downloaded again today and it is fine now. Not sure what went wrong
yesterday during the download - I had tried more than once then, too.
Thanks very much for confirming that it was working outside of our
environment.
- Arkin
On Thu, May 19, 2016 at 6:34 AM Timothy Bish wrote:
> On 05
Hi,
After downloading the 5.13.3 Linux distribution, the MD5 and ASC
verifications failed. I tried more than once.
I used the following page to download:
http://activemq.apache.org/activemq-5133-release.html
Could someone confirm that the signature verification has worked for them?
Thanks,
- Arkin
During an upgrade from 5.9.0 to 5.11.1, ActiveMQ failed to come up on one of
the nodes complaining that the following file could not be found:
/usr/local/activemq-5.11.1/data/anqal1-1-broker/scheduler/legacySchedulerStore/scheduleDB.free
The other node came up fine and did not have that file eithe
I have observed that when sending delayed delivery messages (with
AMQ_SCHEDULED_DELAY values in the header), ActiveMQ does not seem to be
including the delivery in the original transaction. This results in
duplicate messages being delivered in my setup. Here is how I tested:
1. Send a message to a
