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

LegacyLDAPSecuritySettingPlugin listener throws AMQ224086 with Active Directory

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • AMQ 7.8.2.GA
    • None
    • None
    • False
    • False
    • Hide

      This does not reproduce using ApacheDS.

      Show
      This does not reproduce using ApacheDS.

      We have a customer that is using AMQ Broker 7.8.2 with Active Directory. The listener is reporting the follow exception :

      2021-08-18 08:04:14,164 DEBUG [org.apache.activemq.artemis.core.server.impl.LegacyLDAPSecuritySettingPlugin] Performing LDAP search: ***
         filter: (cn=*)
         controls:
            returningAttributes: member
            searchScope: SUBTREE_SCOPE
      2021-08-18 08:04:14,166 ERROR [org.apache.activemq.artemis.core.server] AMQ224086: Caught unexpected exception: javax.naming.OperationNotSupportedException: [LDAP: error code 12 - 00000057: LdapErr: DSID-0C090AFF, comment: Error processing control, data 0, v3839]; remaining name '***'
         at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3321) [rt.jar:1.8.0_292]
         at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3207) [rt.jar:1.8.0_292]
         at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2998) [rt.jar:1.8.0_292]
         at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.getNextBatch(AbstractLdapNamingEnumeration.java:148) [rt.jar:1.8.0_292]
         at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMoreImpl(AbstractLdapNamingEnumeration.java:217) [rt.jar:1.8.0_292]
         at com.sun.jndi.ldap.AbstractLdapNamingEnumeration.hasMore(AbstractLdapNamingEnumeration.java:189) [rt.jar:1.8.0_292]
         at com.sun.jndi.ldap.NamingEventNotifier.run(NamingEventNotifier.java:135) [rt.jar:1.8.0_292]
         at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_292]

      Attached you can find the broker configuration without the sensible information.
      Disabling the listener is not an option, the customer wants to leverage the real-time authorization data update.

        1. broker.xml
          22 kB
          Matteo Golfarini
        2. login.config
          1 kB
          Matteo Golfarini

              rhn-support-jbertram Justin Bertram
              rhn-support-mgolfari Matteo Golfarini (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: