Symptom
To avoid unnecessary downtime due to an unavailable LDAP server, you can configure the LDAP data source for high availability. But when the first server in the list fails, the server application goes down and the server must be restarted to recover, not fulfilling the high availability purpose.
Checking the defaultTraces you find the following exception:
no connection to the ldap server
[EXCEPTION]
java.security.PrivilegedActionException:
-> javax.naming.NamingException: Cannot parse url:
389/<URL to LDAP server> [Root exception is java.net.MalformedURLException: Invalid URI: 389/<URL to LDAP server>]
at java.security.AccessController.doPrivileged(AccessController.java:246)
Read more...
Environment
- SAP NetWeaver Application Server Java - release independent
- User Management Engine
Keywords
LDAP, high availability, failover , KBA , BC-JAS-SEC-UME , User Management Engine , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.