Hi
Thanks for your answer. I think that would be the solution but still baffles
me why you need to give admin rights to your users even for prebuilt
queues/topics
I wrote also an authentication plugin that uses JPA to get user account
information from the DB. It works very nicely but also your i
I think what is happening is that you haven't given everyone all access
rights to the advisory topics. I get a similar stack trace when I don't do
that. Add an ACL with the following "ActiveMQ.Advisory.>" and that should do
the trick.
If you're interested, check out this AMQ security plugin.
h
Hi and thanks for your response
Maybe I should add that the queue is in the startup set
and that in the logs appears as it has been created
This worked fine in AMQ 5.0
Carlos
Dejan Bosanac wrote:
>
> Hi Carlos,
>
> it looks like y
Hi Carlos,
it looks like you don't have "myqueue" created, so ActiveMQ tries to do that
with supplied credentials. Try creating the queue manually if you don't want
to use "admin" priviledges.
Regards
--
Dejan Bosanac
www.scriptinginjava.net
On Wed, May 14, 2008 at 1:55 PM, Carlos Quiroz <
[EMA
