it is a limitation. the thread local allows the different connectors
to find the brokers context, so that network connector and discovered
transports can find an appropriate context.
This makes it simple to configure (broker wide) but difficult to
modify and difficult to have per endpoint ssl optio
Matteo, if you'd like to be able to do this (in a future version of
ActiveMQ), I encourage you to submit an enhancement request in JIRA,
including Gary's description of approximately what would be required to
implement it.
On Jun 25, 2015 4:40 AM, "Gary Tully" wrote:
> it is a limitation. the thr
The fact that durable subscribers created via the web console persist and
ones created via MQTT don't seems like a relevant thread to pull on.
When an MQTT-created subscriber is connected, can you please use JMX to
examine the subscription and see whether the durable property is set to
true? And
I'm trying to understand the behavior you're seeing since from your
description it sounds like there could be multiple problems here, so I've
got some questions.
1. If you send two messages with the RETAINED flag set and then connect
your client, do you get one message or two? (Based on tha
Hello,
We are using apache tomee 1.6 as application server which comes with
activemq 5.9.0 jars OOTB. We use Java 1.7.0_51. A broker is configured to
start up when tomee instance is started. There are various queues configured
under that broker to send/receive messages.
The messages are flowing pr
Jean/Claus,
Thanks for taking time to reply.
This is helpful.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Enterprise-use-for-ActiveMQ-tp4698143p4698180.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thank you for the answers: it is clear now. I'll create the enhancement
request in JIRA and I'll try to implement what Gary suggests.
Many thanks,
matteo
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Rfresh-org-apache-activemq-broker-SslContext-from-disk-jks-content-tp
