Hi Justin,
you're right. We will investigate more closely our login module (redis
itself doesn't seem to be a bottleneck ...but of course it could be the
constantly querying of it).
And we'll also try to perform a stress test session with security disabled.
Just for completeness, following is a st
Addressing is different...
you will need to name your queues and topics with jms.queue and
jms.topic on Artemis 2.0 manually.
There's a difference on that.. I would recommend upgrading everything
to not require that.
there's also a way to specify prefixes on the acceptor. I guess
@Martyn Taylo
Looking to move to 2.0 directly. Are there any pitfalls which we need to be
aware of? Hoping 1.4 JMS client is fully compatible with 2.0 broker.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-Bug-Consume-from-non-durable-jms-topic-tp4724597p4724745.html
Sent fr
In my previous message I referred to the PropertiesLoginModule, but I can see
now that doesn't apply here since you're using a custom login module (i.e.
com.bticino.artemis.RedisLoginModule). You may want to investigate more
closely how the login module is working and if Redis itself might be a
Hi Clebert,
my logging is at the DEBUG level. Inside the artemis.log file, I see calls
to the LoginModule methods when client connects, subscribes and
unsubscribes.
Following the thread trace when it happens during subscription:
"Thread-1 (activemq-netty-threads-1239132915)" #47 daemon prio=5 os_p
I would expect that Artemis would call the LoginModule for those things and any
other place where authentication or authorization is necessary. However, there
is a cache in place for these checks controlled by
which will optimize checks for the same
user/role/permission. Of course, when the s
When you say logging, do you mean the journal?
Logging shouldn't really be an issue unless you're using tracing.
Can you show a thread dump at the time of this happening? a few thread
dumps will usually tell you where most of the CPU is spent if they all
show the same threads under usage.
On Fr
Thanks for giving this guidance for anyone who wants to do this in the
future.
If you'd like to have a less hacky (i.e. config file based) way to do this
in a future version of ActiveMQ, please submit an enhancement request in
JIRA. If you do, please copy and paste the workaround you just describe
Hi Justin,
just an info: by analyzing the log file, it seems that Artemis makes calls
to the login methods (initialize, login and commit, defined in the native
interface of Artemis LoginModule), not only at the login, but also during
subscribtion and unsubscription phases.
We saw this with a clean
After doing these changes, I am able to send new messages form ActiveMQ
console.
But my original task involve sending messages through code not through
console. With this configuration messages are stored in new queue and stuck
at "Messages Enqueued".
Any one have solution for this.
--
View th
OK, so I am answering my own question here (instead of just deleting it all)
in case it might be of help to someone...
I have solved it by doing the following:
* decorate the class SecurityContext
* in the decorator, override method getAuthorizedWriteDests
* in that method, always return an empty
11 matches
Mail list logo
