SAP Knowledge Base Article - Preview

2748383 - AS Java User Management - No connection to the ldap server - Connection timed out to HTTP Proxy - Best Practices for Investigation

Symptom

During datasource configuration in Application Server (AS) Java User Management (UME), while trying to make LDAP over SSL (LDAPs) connection between SAP Portal and LDAP server, connection fails due to http/https proxy set in AS Java. The following exception (partly in screen and full stacktrace in defaultTrace) can be seen:

[...]
No connection to the ldap server, recheck configuration or availability of directory server
[EXCEPTION]
java.security.PrivilegedActionException: javax.naming.CommunicationException: emenhoddcp01.sso.holcim.com:636 [Root exception is java.net.ConnectException: errno: 110 (Connection timed out), error: Connection timed out (local port 56034 to address 0:0:0:0:0:0:0:0, remote port 8080 to address <IP address of proxy> (<proxy host>))]
[...]
Caused by: javax.naming.CommunicationException: emenhoddcp01.sso.holcim.com:636 [Root exception is java.net.ConnectException: errno: 110 (Connection timed out), error: Connection timed out (local port 56034 to address 0:0:0:0:0:0:0:0, remote port 8080 to address <IP address of proxy> (<proxy host>))]
[...]
Caused by: java.net.ConnectException: errno: 110 (Connection timed out), error: Connection timed out (local port 56034 to address 0:0:0:0:0:0:0:0, remote port 8080 to address <IP address of proxy> (<proxy host>))
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
 at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
 at java.net.Socket.connect(Socket.java:837)
 at java.net.Socket.connect(Socket.java:775)
 at java.net.Socket.<init>(Socket.java:672)
 at java.net.Socket.<init>(Socket.java:486)
 at com.sap.security.core.server.https.Utils.getProxySocket(Utils.java:189)
 at com.sap.security.core.server.https.Utils.getProxySocket(Utils.java:129)
 at com.sap.security.core.server.https.Utils.getProxySocket(Utils.java:82)
 at com.sap.security.core.server.https.SecureConnectionFactory.createSocket(SecureConnectionFactory.java:1118)
 at com.sap.security.core.server.https.SecureConnectionFactory.createSocket(SecureConnectionFactory.java:1094)
 at sun.reflect.GeneratedMethodAccessor381.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.jndi.ldap.Connection.createSocket(Connection.java:318)
 at com.sun.jndi.ldap.Connection.<init>(Connection.java:188)
 ... 112 more


Read more...

Environment

  • SAP NetWeaver Application Server Java all versions
  • Configuring LDAP as datasource in UME

Product

SAP NetWeaver Application Server for Java all versions

Keywords

PrivilegedActionException, CommunicationException, ConnectException, LDAP, Connection timed out, local port, to address, remote port, proxy, http proxy, https proxy, no connection to LDAP server , KBA , BC-JAS-SEC-UME , User Management Engine , BC-JAS-SEC , Security, User Management , BC-CST-NI , Network Interface , BC-NET , Network Infrastructure , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.