Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
Hello!
We are using DPAs and have setup WindchillDS to host the MQ information about connection factores, destinations and such.
Aparently this is not working very well in a clustered environment.
It seems to work on slave nodes according to the logs but it fails with below exception when executed on the BGMS.
So my question is:
Which class/classes/tasks to activate in Log4j to view the requests/trafic to LDAP/WindchillDS?
Wed 12/4/13 16:30:43: SessionThread-6: ERROR : wt.adapter.exception Administrator - WTAdapterImpl
Wed 12/4/13 16:30:43: SessionThread-6: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3067)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3013)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2815)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2729)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
Wed 12/4/13 16:30:43: SessionThread-6: at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
Wed 12/4/13 16:30:43: SessionThread-6: at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
...
Best regards,
Peter