Joern Muehlencord created JENKINS-13265:
-------------------------------------------
Summary: Ldap connection failed - jenkins loosing FQDN of ldap
server
Key: JENKINS-13265
URL: https://issues.jenkins-ci.org/browse/JENKINS-13265
Project: Jenkins
Issue Type: Bug
Components: active-directory
Affects Versions: current
Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10,
Apache Tomcat 7.0.14
Reporter: Joern Muehlencord
Attachments: exception.txt
Jenkins is configured to use LDAP login which works perfectly. After some time
- some times directly after restarting tomcat - the login fails. When checking
catalina.out the attached exception is thrown. The reason for the failed login
is clear - Jenkins is configured to connect to ldap.my.domain - but when this
happens Jenkins forgets "ldap" and tries to connect to my.domain only - for
sure this does not work as this is no valid host name.
To fix this, we need to restart Tomcat until it failes again.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
