Hi,
thanks for the hint. I tried it and it didn't work.
There is:
private static final ThreadLocal current
in SslContext. (BTW, during my previous tests, I was setting this to null
after starting each broker to avoid this "caching".)
However, in MQTTNIOSSLTransportFactory, there is
context = S
Hi everybody,
I currently have the following setup:
Network of Brokers with two amq Instances configured with mutual ssl auth
via jaasCertificateAuthenticationPlugin.
For this purpose both amq instances have a transportconnector with ssl
configured.
I would now like to add another transport conn
On 02/15/2017 08:49 AM, beku wrote:
Hi everybody,
I currently have the following setup:
Network of Brokers with two amq Instances configured with mutual ssl auth
via jaasCertificateAuthenticationPlugin.
For this purpose both amq instances have a transportconnector with ssl
configured.
I would
Hi Timothy,
thanks a lot. This is exactly what I was looking for.
Cheers,
beku
-Ursprüngliche Nachricht-
Von: Timothy Bish [mailto:tabish...@gmail.com]
Gesendet: Mittwoch, 15. Februar 2017 15:23
An: users@activemq.apache.org
Betreff: Re: Cert and User Auth on one Broker
On 02/15/201
*ConnectionURL *
failover:(tcp://broker1:61616,tcp://broker2:61616)?andomize=false&jms.useAsyncSend=false&jms.dispatchAsync=false&maxReconnectAttempts=30&maxReconnectDelay=3000&jms.prefetchPolicy.queuePrefetch=1000
Performing a failover by simply turning off broker1 - ./activemq stop
Following
hi,
I am just getting tons of an annoying message from activemq like the
described below when I use the RESTful interface.
The problem doesn't show up when I use an OpenWire interface. It's vanished.
I am using the same camel.xml setup.
The broker seems to work pretty well with the RESTful inte
