Thank you for the input.
I solved the problem of not being able to open multiple Artemis Management
browser tabs by creating unique browser cookies using a class that implements
javax.servlet.ServletContextListener and adding it to the WEB-INF/web.xml file
in Artemis's console.war like so:
Hello,
Is there a way to configure a clustered node with a live-only ha-policy to
participate in quorum voting? I'm experimenting with a cluster containing 3
live/backup pairs and a live-only node. The live-only node reports the
following when one of the live nodes from a live/backup pair shuts
> But can users be created (and deleted) on-demand?
I'm not exactly sure what you mean by "on-demand," but users can be created
administratively on a running broker via management. This can be done via
the "artemis user" command, the web console, Jolokia, etc. You'll need to
use the PropertiesLogi
Hi,
we have very similar requirements. You can search this mailing list for my
recent questions and answers from others for details.
Basically we have chosen ActiveMQBasicSecurityManager as a backend, and we are
creating users, their permissions and queues on-demand, using
activemq.management
We have a more complicated scenario where we use Artemis and are
currently struggling with some security-related problems. Let me try to
sketch our setup:
- Several producers put work items into queues in Artemis. Every
producer uses a dedicated queue, e.g. "jobs.123" where 123 is the
unique produ
