Were getting closer but not quite there.
The following error keeps coming up when trying to send ActiveMQ a message.
I can't seem to find what the issue is or how to get deeper into
diagnosising the problem.
All the configs seem correct can you please take a look and see if you
happen to see someth
I'm currently doing the same thing in ActiveMQ 5.15.2.
Can you set the level for
"org.apache.activemq.artemis.spi.core.security.jaas" to debug/trace to get
the information you're after?
Jon
On Wed, May 2, 2018 at 5:26 PM, mtod wrote:
> Would you happen to know how yo log the LDAP calls to assi
Would you happen to know how yo log the LDAP calls to assist in diagnosing
issues?
I'm not seeing any JAAS appenders
Mike
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Thanks
I have used AD LDAP with other systems but this one just seems to be giving
me issues.
I'll check out your config and see if I can figure out where I'm going
wrong.
Mike
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Thanks Tim. I am using Active MQ 5.14.2. I think its a bug in this version.
When I use latest 5.15.3, I don't see that behaviour.
I am using Queue not a topic.
Yes, my messages are flagged as persistent when sent. Message expiration is
not a factor here. The messages are indeed available whe
I've successfully configured ActiveMQ Artemis with LDAP / AD. Example
configuration below:
ADLogin {
org.apache.activemq.artemis.spi.core.security.jaas.LDAPLoginModule required
debug=true
initialContextFactory="com.sun.jndi.ldap.LdapCtxFactory"
connectionURL=
Hello,
As well as some previous issues [1] I have some problems with my Artemis
cluster. My setup [2] is a symmetric two node cluster of colocated instances
with scaledown. As well as the node restart causing a problematic state in
replication [1] there are other issues, namely:
1) After runni
