Thank You Justin
--
View this message in context:
http://activemq.2283324.n4.nabble.com/User-privileges-exception-thrown-from-jaas-Authorization-plugin-format-for-jaas-artemis-tp4719410p4719473.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Is the amount of time different when the server goes down due to a graceful
shutdown vs. a hard kill (kill -9 or equivalent)? Could what you're seeing
be related to the amount of time it takes to detect that a TCP connection
has been severed without a clean shutdown?
Tim
On Nov 23, 2016 9:58 PM,
Hi all,
I'm running a 2 node Artemis cluster in replication mode. Everything is
running as it should, but we noticed a variance in the time it takes from
the 'backup' server to become 'live' when the primary server goes down. The
failover time can take a short as 10~20 seconds to upto a few minute
Your problem is indeed related to authorization. Your user is able to login but
does not have permission (i.e. is not authorized) to create a durable queue.
As with your previous question, the documentation should provide the help you
need. The link I provided previously [1] should have the in
I tried to implement a custom JAAS authentication module with
apache-artemis-1.3.0.
In bootstrap.xml,
In login.config,
CustomLogin {
com.activemq.core.CustomLoginModule Sufficient
core.url="http://localhost:8080/jaas";;
};
Call flow seems to get executed properly. LoginModule.l
Thanks a lot Justin for the quick precise reply.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Links-to-any-introductory-articles-for-jaas-artemis-integration-tp4719375p4719394.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
