Very Slow Running BIP Reports After JVM Failure and OID 11g Merge Patch 22313537. Log Error Stack Shows: [Root exception is java.net.SocketTimeoutException: connect timed out]
(Doc ID 2156906.1)
Last updated on APRIL 12, 2021
Applies to:
Oracle Internet Directory - Version 11.1.1.7.0 and laterBI Publisher (formerly XML Publisher) - Version 12.0 and later
Information in this document applies to any platform.
Symptoms
Business Intelligence Published (BIP) integrated with Oracle Internet Directory (OID) 11g.
After the following issue:
When scheduling a report on BIPublisher, a connection is made from the WebLogic (WLS) Managed Server to the AdminServer and some LDAP data is exchanged. If this connection is initiated when the AdminServer is not running, a TCP reset is sent back from the interface to which the AdminServer IP is bound and processing continues. However, if this connection is initiated whilst the AdminServer interface is down (during a failure scenario) the Managed Server waits for an operating system level TCP time-out before returning a Job ID.
Was resolved by applying Patch 22313537 (merge request on top of 11.1.1.7.0 for unpublished Bugs 22119211 22149715), noticed a very slow processing of BIP reports on the remaining JVMs after a JVM (with AdminServer) failure.
The stacktrace converge on the method call oracle.xdo.servlet.security.JPSSecurityHandler.getPrincipal and all subsequent calls are the same. In the scenario, the calll to oracle.xdo.servlet.security.JPSSecurityHandler.getPrincipal originates in oracle.xdo.server.impl.StdSecurityManager.login.
This is an excerpt from the error stack:
[oracle.xdo] [tid: 6362] [userId: <anonymous>] [ecid: <ECID#>:-8000-000000000009354c,0] [APP: bipublisher#11.1.1] oracle.security.idm.OperationFailureException: javax.naming.CommunicationException:
<HOSTNAME>:38001 [Root exception is java.net.SocketTimeoutException: connect timed out][[
at oracle.security.idm.providers.stdldap.JNDIPool.acquireConnection(JNDIPool.java:99)
at oracle.security.idm.providers.stdldap.LDIdentityStoreFactory.acquireConnection(LDIdentityStoreFactory.java:763)
at oracle.security.idm.providers.stdldap.LDIdentityStore.acquireConnection(LDIdentityStore.java:770)
at oracle.security.idm.providers.stdldap.LDIdentityStore.searchUser(LDIdentityStore.java:522)
at oracle.security.idm.providers.stdldap.LDIdentityStore.searchUser(LDIdentityStore.java:605)
at oracle.xdo.security.jps.JPSManager.getUser(JPSManager.java:602)
at oracle.xdo.security.jps.JPSManager.getUserProfile(JPSManager.java:578)
at oracle.xdo.security.jps.JPSManager.getUserEmail(JPSManager.java:588)
at oracle.xdo.security.JPSValidator.getUserEmailAddress(JPSValidator.java:477)
at oracle.xdo.servlet.security.JPSSecurityHandler.handleUserPreferences(JPSSecurityHandler.java:126)
at oracle.xdo.servlet.security.JPSSecurityHandler.getJPSPrincipal(JPSSecurityHandler.java:267)
at oracle.xdo.servlet.security.JPSSecurityHandler.getPrincipal(JPSSecurityHandler.java:78)
at oracle.xdo.server.impl.StdSecurityManager.login(StdSecurityManager.java:19)
...
Caused by: javax.naming.CommunicationException:
<HOSTNAME>:38001 [Root exception is java.net.SocketTimeoutException: connect timed out]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:216)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:136)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1608)
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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:153)
at oracle.security.idm.providers.stdldap.JNDIPool.acquireConnection(JNDIPool.java:91)
... 60 more
Caused by: java.net.SocketTimeoutException: connect 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:392)
at java.net.Socket.connect(Socket.java:579)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:316)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:203)
... 73 more
Changes
Patch 22313537 is already applied.
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 |
| References |