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
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
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
Adding security-settings was the work-around provided on the JIRA.
Justin
On Wed, Oct 11, 2017 at 1:44 PM, Clebert Suconic
wrote:
> What about adding the Security Settings for that address?
>
> On Wed, Oct 11, 2017 at 2:08 PM, Justin Bertram
> wrote:
> > Could you provide the full stack-trace
What about adding the Security Settings for that address?
On Wed, Oct 11, 2017 at 2:08 PM, Justin Bertram wrote:
> Could you provide the full stack-trace?
>
> Also, it's worth noting that a work-around for the issue was posted on the
> aforementioned JIRA a day after it was opened back in Februar
Could you provide the full stack-trace?
Also, it's worth noting that a work-around for the issue was posted on the
aforementioned JIRA a day after it was opened back in February.
Justin
On Mon, Oct 9, 2017 at 2:19 AM, martin_activeMQ wrote:
> Hi Justin,
>
> I'm using the latest available vers
Hi Justin,
I'm using the latest available version 1.5.5 and it seems that the problem
is reproducible. Any suggestion to workaround this limitation?
address=activemq.notifications,properties=TypedProperties[_AMQ_User=X,_AMQ_Address=$sys.mqtt.queue.qos2..$sys.mqtt.queue.qos2.,_
Essentially you just need to change the Artemis modules in Wildfly (i.e.
"org.apache.activemq.artemis",
"org.apache.activemq.artemis.protocol.stomp",
"org.apache.activemq.artemis.protocol.hornetq", &
"org.apache.activemq.artemis.protocol.amqp") to use the jar files from the
1.5.5 distribution. The
could you tell me how I could change from version seeing that I am using the
native artemis of wildfly-10.1.0.Final ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/User-null-does-not-have-permission-CREATE-DURABLE-QUEUE-on-address-sys-mqtt-queue-qos2-JavaSample-tp472912
g this when I try to connect my client:
> WARN [org.apache.activemq.artemis.core.protocol.mqtt] (Thread-2
> (activemq-netty-threads-164875171)) Error processing Control Packet,
> Disconnecting ClientAMQ119032: User: null does not have
> permission='CREATE_DURABLE_QUEUE' on ad
does not have
permission='CREATE_DURABLE_QUEUE' on address
$sys.mqtt.queue.qos2.JavaSample.
I added an application user to wildfly, I gave him 'guest' as role, and in
my standalone-full.xml, I found this:
So I tried to connect my client with username and password (creat
11 matches
Mail list logo
