My Oracle Support Banner

Testing A Connection From Policy Studio Fails With "Connection Timed Out" (Doc ID 1934350.1)

Last updated on MARCH 02, 2021

Applies to:

Oracle API Gateway - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

The "Test Connection" funtionality from Policy Studio fails with "Connection timed out".

 

Example messages when testing an LDAP Connection from Policy Studio:

DEBUG   <TIMESTAMP> [<THREAD ID>] url : [url{ldap://<IP ADDRESS>:<PORT>}]
DEBUG   <TIMESTAMP> [<THREAD ID>] cacheTimeout : [cacheTimeout{300000}]
DEBUG   <TIMESTAMP> [<THREAD ID>] cacheSize : [cacheSize{8}]
DEBUG   <TIMESTAMP> [<THREAD ID>] authType : [authType{SIMPLE}]
DEBUG   <TIMESTAMP> [<THREAD ID>] userName : [userName{<CN FOR USER>}]
DEBUG   <TIMESTAMP> [<THREAD ID>] authRealm : [authRealm{}]
DEBUG   <TIMESTAMP> [<THREAD ID>] sslEnabled : [sslEnabled{0}]
DEBUG   <TIMESTAMP> [<THREAD ID>] sslCertificate : [sslCertificate{-1}]
DEBUG   <TIMESTAMP> [<THREAD ID>] Setting default(s) for field: cacheTimeout
DEBUG   <TIMESTAMP> [<THREAD ID>] Setting default(s) for field: cacheSize
DEBUG   <TIMESTAMP> [<THREAD ID>] In ScreenAttributeHolder.validateAttrs
ERROR   <TIMESTAMP> [<THREAD ID>] java exception:
javax.naming.CommunicationException: <IP ADDRESS>:<PORT> [Root exception is java.net.ConnectException: Connection timed out]
    at com.sun.jndi.ldap.Connection.<init>(Connection.java:224)
    at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:136)
    at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1600)
    at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2698)
    at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
    at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
    at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
    at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
    at javax.naming.InitialContext.init(InitialContext.java:242)
    at javax.naming.InitialContext.<init>(InitialContext.java:216)
    at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:101)
    at com.vordel.common.ldap.ContextCache$CachedContext.<init>(ContextCache.java:47)
    at com.vordel.common.ldap.ContextCache$1.factory(ContextCache.java:72)
    at com.vordel.common.ldap.ContextCache$1.factory(ContextCache.java:57)
[...]
Caused by: java.net.ConnectException: Connection timed out
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
    at java.net.Socket.connect(Socket.java:579)
    at java.net.Socket.connect(Socket.java:528)
    at java.net.Socket.<init>(Socket.java:425)
    at java.net.Socket.<init>(Socket.java:208)
    at com.sun.jndi.ldap.Connection.createSocket(Connection.java:366)
    at com.sun.jndi.ldap.Connection.<init>(Connection.java:201)
    ... 64 more

 

Changes

The "Test Connection" functionality in Policy Studio creates a connection from Policy Studio to the backend server.
It does not test the connection from the Gateway instance to the backend server.

As Policy Studio is typically running on a different host, additional firewall configurations might be necessary to allow the connection from Policy Studio to the backend server.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.