Re: User: null does not have permission='CREATE_DURABLE_QUEUE' on address $sys.mqtt.queue.qos2.JavaSample

2017-10-30 Thread martin_activeMQ
As far as I know, they left left that use case and they will not support it. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: User: null does not have permission='CREATE_DURABLE_QUEUE' on address $sys.mqtt.queue.qos2.JavaSample

2017-10-30 Thread Justin Bertram
I'm only interested in the part of the stack-trace that covers Artemis code. Assuming they haven't made significant modifications of their own to Artemis (for whatever reason) there's really no security risk here. Also, have they tried the work-around on the JIRA? Justin

Re: User: null does not have permission='CREATE_DURABLE_QUEUE' on address $sys.mqtt.queue.qos2.JavaSample

2017-10-30 Thread martin_activeMQ
Hi Justin, Sorry for the late reply, but I'm not able to provide the full stack trace. The problem was reported by a customer and according their security policy they are not allowed to provide me that information. Best Regards, Martin -- Sent from: http://activemq.2283324.n4.nabble.com/Active

Re: [Artemis] - Can last value queue be sent to multiple consumers?

2017-10-30 Thread Martyn Taylor
Hi Lionel, If I understand your use case correctly, then MQTT has a feature that does exactly what you're trying to achieve. Retained messages. "When a workstation connects, I want it to be able to get the most recent value immediately." A producer can mark a message as "retain". The broker ke