Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-3818

Unable to use LDAP Connection pooling in LDAPLoginModule

XMLWordPrintable

    • Hide

      To reproduce the issue, see the README file in the  attached reproducer.zip

      The zip files contains instructions to set up:

      • An embedded LDAP server
      • The AMQ 7 configuration
      • The EAP 7 configuration
      • A quickstart application which contains an MDB

       

      Show
      To reproduce the issue, see the README file in the  attached reproducer.zip The zip files contains instructions to set up: An embedded LDAP server The AMQ 7 configuration The EAP 7 configuration A quickstart application which contains an MDB  

      The scenario is AMQ configured with LDAP based Security Settings to send/consume messages from EAP.
      To avoid a performance penalty, the following settings have been added in login.config:

      activemq {
         org.apache.activemq.artemis.spi.core.security.jaas.LDAPLoginModule required
             ...
             connectionPool=true
             connectionTimeout="100000";
      };
      

      That works to reduce the number of LDAP authentications when a message is sent, yet it does not to reduce authentication for consumers.
      As a matter of fact, it produces a number of LDAP authentication attempt for each MDB deployed (if CPU=2, there are 16 login attempts for each MDB deployed).
      This is causing a rollback of deployments for applications using a large number of MDBs.

              rhn-support-jbertram Justin Bertram
              fmarchio@redhat.com Francesco Marchioni (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: