What could have gone wrong with LDAP connection on WAS?
We are not looking for a resolution as the issue has been resolved: But we are looking for an explanation of what could have gone wrong, out of sync.
We recently switch to WAS from Tomcat for our RTC/RRC 5.0.2 on Windows server 2008, with difficulty, but running OK for a while.
All of a sudden we lost the user import functionality, as we can no longer search for a user in LDAP, when click search for any user we would get the error message below:
"An error response was received from the Jazz Team Server. Status=400. Message: CRJAZ0742I Unable to connect to the LDAP directory server. Verify that the server application is configured properly and that the LDAP server is reachable"
When we test for connection from the WAS Admin Console we got an error too:
=================* Test LDAP connection from WAS (console)
SECJ7340E: Exception raised trying to connect to LDAP server: NamingException: ent.rt.csaa.com:389 java.net.ConnectException: Connection refused: connect
we started our RTC DR server, on the same domain, and found that we did not encounter this issue there, we hence rebooted the PRD appServer and resolved the issue.
Any idea what could have gone out of sync? or wrong?
|
Accepted answer
It's not about "out of sync", but rather how WAS connects to the LDAP server. As far as I know, WAS connects to the LDAP server only when starting up, at least if you follow the steps provided in the Jazz documentation. So, if the LDAP server somehow gets recycled, or the network is interrupted, all existing LDAP connection between WAS and LDAP will be broken, and you will see the issue in the OP.
long TRUONG selected this answer as the correct answer
Comments
long TRUONG
commented Jan 13 '17, 11:39 a.m.
Ah! We did not need a reboot, just a WAS service restart would have been sufficient.
Thx Don.
long TRUONG
commented Jan 13 '17, 12:56 p.m.
We did run into same issue again, but with a different cause, which was sort of self resolved shortly afterwards:
|
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.