Connection has been administratively disabled by console/admin command in EBS 12.2.4 Weblogic 10.3.6

APPLIES TO:

Oracle Applications Technology Stack - Version 12.2 to 12.2.5 [Release 12.2]
Information in this document applies to any platform.

SYMPTOMS

Below message from weblog Adminserver log files. 

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 

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 Thu Jun 15 05:50:09 IST 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:225) 
at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:201) 
at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:176) 
at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:151) 
at oracle.apps.jtf.cache.GenericCacheLoader.load(Unknown Source) 
at oracle.ias.cache.CacheLoader.callLoad(CacheLoader.java:60) 

SOLUTION

Action Plan

Inactive Connection Timeout =3600 

Login to Weblogic Server Administration Console. Default: http://localhost:7001/console 
Select 'Lock and Edit' (if WebLogic server is a Production Mode implementation) 
Go to Home > Summary of Servers > AdminServer, Tuning tab. 
Change the Stuck Thread Max Time from 3600 to 900. 
Change the Stuck Thread Timer Interval from 3600 to 100 
Go to Overload tab 
Change the Max Stuck Thread Time from 600 to 900. 
Change the Stuck Thread Count 0 to 20. 
Save and Activate Changes. 
Restart the WebLogic server.