It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,478
×6,035
×4,321
×88

question asked: Oct 07 '16, 8:50 a.m.
question was seen: 6,061 times
last updated: Oct 12 '16, 8:16 a.m.

Related questions

Intermittent LDAP Connection Timeout/Reset using CLM 6.0.2 and WebSphere Liberty Profile

0
Lenny Basuino (15●1●3) | asked Oct 07 '16, 8:50 a.m.
We are plagued with intermittent LDAP connection timeout/reset when used with CLM 6.0.2 with WebSphere Liberty Profile.  The same LDAP server is used by other Web servers running standalone ClearQuest and RequisitePro without any issue.

Looking for the answer, but will accept suggestions.
TIA!

LennyB
Comments
Donald Nong commented Oct 10 '16, 1:30 a.m.

Where do you see the timeout/reset error message? In CLM application log files or Liberty log file? What exactly is the error?

Lenny Basuino commented Oct 10 '16, 10:35 a.m.

The messages.log has:

00005dc7 com.ibm.ws.security.wim.registry.util.LoginBridge E com.ibm.websphere.security.wim.exception.WIMSystemException: CWIML4520E: The LDAP operation could not be completed.  The LDAP naming exception javax.naming.CommunicationException: <domain>:<port> [Root exception is java.net.ConnectException: Connection timed out: connect] occurred during processing.

and then going to the ffdc log:

Stack Dump = javax.naming.CommunicationException: <domain>:<port> [Root exception is java.net.ConnectException: Connection timed out: connect]
  at com.sun.jndi.ldap.Connection.<init>(Connection.java:229)

and also seen in ffdc log (other times):

Stack Dump = javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name 'dc=<xx>,dc=<xx>,dc=<xx>'
  at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:2016)

Donald Nong commented Oct 10 '16, 7:02 p.m.

My best guess is that it could be the particular server or the version of Liberty. You may get a better response by asking the question in the dW Answers forum.
https://developer.ibm.com/answers/

Or you can contact Support.

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Lenny Basuino (15●1●3) | answered Oct 12 '16, 8:16 a.m.
We have a possible explanation and fix for our issue.  (I'll mark it accepted after it is working for awhile).  We have a load balancer in front of several LDAP servers.  We are thinking this is causing the problem and have reconfigured the LDAP configuration to point to a specific LDAP server and use the others as fail over servers as described here:
http://www.ibm.com/support/knowledgecenter/en/SSD28V_8.5.5/com.ibm.websphere.wlp.core.doc/ae/twlp_sec_ldap.html

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.