With individual acknowledgement, if you don't acknowledge the message it
will be kept on the broker and tracked until you either acknowledge it or
close the consumer. If you close the consumer it should be redelivered to
another consumer.
With transactions you need to explicitly call commit or
On Fri, 12 Jun 2015 16:08:05 -0600, Tim Bain
tb...@alumni.duke.edu wrote:
Just to be 100% clear what should the behaviour be if I use
INDIVIDUAL_ACKNOWLEDGE (vs SESSION_TRANSACTED) and have not
acknowledged the message?
It sounds like you can reproduce this reliably; can you submit a bug report
Hi folks,
I'm running 5.11.1 and trying to get ActiveMQ to authenticate users against an
LDAP via JAAS. I'm trying out org.apache.activemq.jaas.LDAPLoginModule but
noticing a couple of issues.
First, it doesn't seem to re-use LDAP connections (i.e. pooling) and on top of
that, it doesn't
It seems pretty clear that the assumption that acquiring a single file lock
without doing any further checks will provide thread-safety in all cases is
not an accurate one.
As I see it, here are the failures of the existing approach:
- Failure #1 is that when an NFS failure occurs, the master
I have developed a custom BrokerPlugin using BrokerFilter for Security
purposes.
The plugin performs its own custom authentication in the addConnection()
method.
During the authentication we return an authorization parameter(String) that
allows
us to identify which topic(s) a client is allowed
I have developed a custom BrokerPlugin using BrokerFilter for Security
purposes.
The plugin performs its own custom authentication in the addConnection()
method.
During the authentication we return an authorization parameter(String) that
allows
us to identify which topic(s) a client is allowed
