Ah, Thanks for the hint. Where would you set the cipher? Is it part of the
connecting string as well? I couldn't find much documentation online.
Thanks,
Oliver
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-Enforce-TLS-1-1-or-1-2-tp4690568p4693340.html
Sent from
https://issues.apache.org/jira/browse/AMQ-5665
On Mon, Mar 16, 2015 at 1:32 PM, Kevin Burton wrote:
> Looks like there's a regression in >= 5.11.0.
>
> Advisories fail to fire.
>
> It looks like it’s a bug with MemoryTransactionStore. Switching to
> persistent brokers fixes the problem.
>
> It’s
Looks like there's a regression in >= 5.11.0.
Advisories fail to fire.
It looks like it’s a bug with MemoryTransactionStore. Switching to
persistent brokers fixes the problem.
It’s because addMessage calls:
} else {
destination.addMessage(null, message);
}
.. with a
I'm trying to migrate to ActiverMQ 5.11 using the new dynamic routing option.
Using 5.10 I was able to place a name space in an external camel file such
as:
http://camel.apache.org/schema/spring";
xmlns:km="http://xsdrepo.foundationmedicine.com/messaging/esb";>
This issue happens when my URI is:
failover:(tcp://MACHINE_1:61616,tcp://MACHINE_2:61616)?randomize=false&useExponentialBackOff=false&initialReconnectDelay=1000&startupMaxReconnectAttempts=40&timeout=3
When I change to only 1 machine, the number of threads stays stable:
failover:(tcp://MACHINE
Thank you for the reply Tim.
I think we are going with a maser/slave setup at each dc but the main hub
datacenter will have the config that notes all other data centers. Is it
recommended to do the same with the other activemq.xml configs to point back
to the hub, in case the hub goes down?
We
