-
1. Re: LDAP and 3rd party mq provider
neil_g_avery Apr 14, 2003 4:02 PM (in response to neil_g_avery)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
omponentContext.java:152)
at com.sun.jndi.toolkit.ctx.AtomicContext.c_resolveIntermediate_nns(Atom
icContext.java:340)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_resolveIntermediate(Compo
nentContext.java:377)
at com.sun.jndi.toolkit.ctx.ComponentContext.p_lookup(ComponentContext.j
ava:511)