1 Reply Latest reply on Apr 14, 2003 4:02 PM by Neil Avery

    LDAP and 3rd party mq provider

    Neil Avery Newbie

      We been integrating our JMS product with JBoss and so far have successfully created the Adaptor, a Daemon service and have managed to allow queue/topic lookup to use our specified JNDI etc. So far so good!

      Our product supports LDAP and would like to carry that support through into JBOSS. That is to say that queue/DLQ lookup works with LDAP - where the request is translated into cn=queue,cn=DLQ.

      The only resolve we can conclude is to write a 3rd part intermediary layer (interceptor to LDAP) that provides this translation.
      queue/DLQ => cn=queue,cn=DLQ

      Can anyone help ?

        • 1. Re: LDAP and 3rd party mq provider
          Neil Avery Newbie

          Some further information. Our JMSAdaptor provides an LdapContext to JBoss that MdBeans use to lookup destinations. After changing factory names by adding a cn=XaTopicConnectionFactory etc jboss commences startup until it tries to lookup a queue or topic instance.

          The topic/queue prefix assumes that "/" notation is acceptable to the Context being used. However for LDAP this causes problems as it uses different syntax. The following exception is thrown,

          20:55:23,330 ERROR [DLQHandler] Initialization failed
          javax.naming.InvalidNameException: queue: [LDAP: error code 34 - Invalid DN Synt
          ax]; remaining name 'queue/DLQ'
          at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2855)
          at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2669)
          at com.sun.jndi.ldap.LdapCtx.c_lookup(LdapCtx.java:944)
          at com.sun.jndi.toolkit.ctx.ComponentContext.c_resolveIntermediate_nns(C
          at com.sun.jndi.toolkit.ctx.AtomicContext.c_resolveIntermediate_nns(Atom
          at com.sun.jndi.toolkit.ctx.ComponentContext.p_resolveIntermediate(Compo
          at com.sun.jndi.toolkit.ctx.ComponentContext.p_lookup(ComponentContext.j