java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Thu Nov 06 17:53:10 GST 2014[[

Oracle Community | K.S.V. Adiga | 2 years ago
  1. 0

    Configured DMZ in R12.2.3 : Connection has been administratively disabled by console/admin command.

    Oracle Community | 2 years ago | K.S.V. Adiga
    java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Thu Nov 06 17:53:10 GST 2014[[
  2. 0

    Hi, We are continuously encountering issues when the Quartz is giving us the following error when deployed in web logic 11g being used in Clustered env.. When the below mentioned error occurs , it looks like a DB freeze . Quartz is not able to perform an DB related activities( No write and update is allowed on the DB). If we check the DB instances for any Locks - During the 1st few occurrence , we did find lock on QRTZ_LOCKS table but other times there was no locks. We tried to clear the active sessions , but we see that new SESSIONs were getting created as soon as the old ones were flushed. Any probable reason for this. Due to this session being created , we were unable to stop or undeploy our application using QUARTZ from the Weblogic servers. We also notice contention with the QRTZ_LOCKS table (that has entries for the STATE_ACCESS and TRIGGER_ACCESS). Attaching the exception trace we get : {noformat} 015-09-21 07:02:02|ERROR|org.quartz.impl.jdbcjobstore.JobStoreTX|JobScheduler_QuartzSchedulerThread|Couldn't rollback jdbc connection. Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Sep 21 07:02:00 GMT+00:00 2015 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 org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:96) at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:113) at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3770) at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggersFired(JobStoreSupport.java:2887) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:326) java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Sep 21 07:02:00 GMT+00:00 2015 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 org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:96) at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:113) at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3770) at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggersFired(JobStoreSupport.java:2887) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:326). {noformat} Also below is the configuration used in quartz.properties (Across the multiple node in the clustered snv): {code} org.quartz.scheduler.instanceName=Scheduler1 org.quartz.scheduler.instanceId=AUTO org.quartz.scheduler.rmi.export=false org.quartz.scheduler.rmi.proxy=false org.quartz.scheduler.wrapJobExecutionInUserTransaction=false org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool org.quartz.threadPool.threadCount=50 org.quartz.threadPool.threadPriority=5 org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread=true org.quartz.jobStore.isClustered=true org.quartz.jobStore.misfireThreshold=60000 org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate org.quartz.jobStore.dataSource=MyDs org.quartz.dataSource.MyDs.jndiURL=jdbc.quartz {code} So could you please help us with this issue. This is occurring more often in our environment and the only solution that we have right now is to recreate the Quartz schema each time this issue occurs. Help is much appreciated. Thanks , Jidhu

    Terracotta Project Issue Tracker | 1 year ago | Edward Sweeney
    java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Sep 21 07:02:00 GMT+00:00 2015
  3. 0

    Hi, We are continuously encountering issues when the Quartz is giving us the following error when deployed in web logic 11g being used in Clustered env.. When the below mentioned error occurs , it looks like a DB freeze . Quartz is not able to perform an DB related activities( No write and update is allowed on the DB). If we check the DB instances for any Locks - During the 1st few occurrence , we did find lock on QRTZ_LOCKS table but other times there was no locks. We tried to clear the active sessions , but we see that new SESSIONs were getting created as soon as the old ones were flushed. Any probable reason for this. Due to this session being created , we were unable to stop or undeploy our application using QUARTZ from the Weblogic servers. We also notice contention with the QRTZ_LOCKS table (that has entries for the STATE_ACCESS and TRIGGER_ACCESS). Attaching the exception trace we get : {noformat} 015-09-21 07:02:02|ERROR|org.quartz.impl.jdbcjobstore.JobStoreTX|JobScheduler_QuartzSchedulerThread|Couldn't rollback jdbc connection. Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Sep 21 07:02:00 GMT+00:00 2015 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 org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:96) at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:113) at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3770) at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggersFired(JobStoreSupport.java:2887) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:326) java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Sep 21 07:02:00 GMT+00:00 2015 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 org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:96) at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:113) at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3770) at org.quartz.impl.jdbcjobstore.JobStoreSupport.triggersFired(JobStoreSupport.java:2887) at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:326). {noformat} Also below is the configuration used in quartz.properties (Across the multiple node in the clustered snv): {code} org.quartz.scheduler.instanceName=Scheduler1 org.quartz.scheduler.instanceId=AUTO org.quartz.scheduler.rmi.export=false org.quartz.scheduler.rmi.proxy=false org.quartz.scheduler.wrapJobExecutionInUserTransaction=false org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool org.quartz.threadPool.threadCount=50 org.quartz.threadPool.threadPriority=5 org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread=true org.quartz.jobStore.isClustered=true org.quartz.jobStore.misfireThreshold=60000 org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate org.quartz.jobStore.dataSource=MyDs org.quartz.dataSource.MyDs.jndiURL=jdbc.quartz {code} So could you please help us with this issue. This is occurring more often in our environment and the only solution that we have right now is to recreate the Quartz schema each time this issue occurs. Help is much appreciated. Thanks , Jidhu

    Terracotta Project Issue Tracker | 1 year ago | Edward Sweeney
    java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Mon Sep 21 07:02:00 GMT+00:00 2015
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Seeking for advice on exception: java.sql.SQLRecoverableException: IO Error: Read failed: Connection timed out

    Oracle Community | 3 years ago | User771952-Oracle
    java.sql.SQLException: Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Fri May 16 10:02:09 UTC 2014
  6. 0

    Issue with Weblogic Connection Pool

    Oracle Community | 7 years ago | 757905
    java.sql.SQLException: Connection has been administratively disabled. Try later.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.sql.SQLException

      Connection has been administratively disabled by console/admin command. Try later. java.lang.Exception: It was disabled at Thu Nov 06 17:53:10 GST 2014[[

      at weblogic.jdbc.common.internal.ConnectionEnv.disable()
    2. weblogic.jdbc.common
      ConnectionEnv.disable
      1. weblogic.jdbc.common.internal.ConnectionEnv.disable(ConnectionEnv.java:357)
      1 frame
    3. weblogic.jdbc.wrapper
      PreparedStatement.executeQuery
      1. weblogic.jdbc.wrapper.JDBCWrapperImpl.invocationExceptionHandler(JDBCWrapperImpl.java:127)
      2. weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:152)
      2 frames
    4. oracle.apps.fnd
      GenericCacheLoader.load
      1. oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:225)
      2. oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:201)
      3. oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:176)
      4. oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:151)
      4 frames
    5. oracle.apps.jtf
      GenericCacheLoader.load
      1. oracle.apps.jtf.cache.GenericCacheLoader.load(Unknown Source)
      1 frame
    6. oracle.ias.cache
      CacheAccess.get
      1. oracle.ias.cache.CacheLoader.callLoad(CacheLoader.java:60)
      2. oracle.ias.cache.CacheHandle.findObject(CacheHandle.java:1532)
      3. oracle.ias.cache.CacheHandle.locateObject(CacheHandle.java:1118)
      4. oracle.ias.cache.CacheAccess.get(CacheAccess.java:877)
      4 frames
    7. oracle.apps.jtf
      CacheManager.getInternal
      1. oracle.apps.jtf.cache.IASCacheProvider.get(IASCacheProvider.java:771)
      2. oracle.apps.jtf.cache.CacheManager.getInternal(CacheManager.java:4802)
      2 frames