Firewall BLACKOUT and JDBC connections with Oracle Applications 12.2 Due To Error 'oracle.apps.jtf.base.resources.FrameworkException: Connection has been administratively disabled by console/admin command. Try later.' (Doc ID 2253795.1)

Last updated on OCTOBER 19, 2024

Applies to:

Oracle E-Business Suite Technology Stack - Version 12.2 and later
Information in this document applies to any platform.

Symptoms

It is common in the advanced topologies to isolate the web tier(s) from the database tier(s) using one or more firewalls. A potential problem is that firewalls are typically configured to time out unused connections after one hour. With an E-Business suite instance, this can result in JDBC connections being disconnected without warning to the application. At this point, the connection is blacked out.

After the blackout has occurred, further JDBC activity causes an error to the application. The only recovery is to bounce the managed server. The error seen from the user perspective can be any kind of error, but basically implies that there is no connection to the database.

Typically what is seen in the manager server diagnostic log is something similar to the following:

Caused by: oracle.apps.jtf.base.resources.FrameworkException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Apr 10 18:44:56 GMT 2017
at weblogic.jdbc.common.internal.ConnectionEnv.disable(ConnectionEnv.java:357)
at weblogic.jdbc.wrapper.JDBCWrapperImpl.invocationExceptionHandler(JDBCWrapperImpl.java:127)
at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:152)
at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:249)
at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:225)