java.sql.SQLException: The database is already in use by another process [java] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:92) [java] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1070) [java] Full thread dump: [java] Full thread dump: "Thread-5" daemon prio=5 tid=0x8aacaf8 nid=0x6b4 runnable [0x8dcf000..0x8dcfdbc]

Oracle Community | 3004 | 1 decade ago
  1. 0

    SchemaTool failure causes Ant to hang

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: The database is already in use by another process [java] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:92) [java] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1070) [java] Full thread dump: [java] Full thread dump: "Thread-5" daemon prio=5 tid=0x8aacaf8 nid=0x6b4 runnable [0x8dcf000..0x8dcfdbc]
  2. 0

    Stuck Thread problem with XA Connections

    Oracle Community | 10 years ago | 666705
    java.sql.SQLException: [BEA][Oracle JDBC Driver]Internal error: Net8 protocol error..> When this happens, that thread seems to lock pretty much for good. The web user never gets a response, and if we run a thread dump, we can see that the thread is stuck. (see below). DBAs have confirmed that the connection is no longer active, so the thread seems to be stuck somewhere in the driver. 2) We do not get the Net8 error. Instead, the transaction continues inexplicably (it should have timed out) to the next piece of SQL, which it then attempts to run. I am not as clear as to what is going on in this case, but it appears that it makes another request on the same connection, but now the database responds unbelievably slowly (if at all.) Sometimes the Net8 error occurs at a later time. System is Weblogic 9.2. We are using the BEA XA driver for Oracle. This problem exists both in a clustered environment as well as on local single-server environments. This is a stack trace we get in the log: <May 9, 2007 11:16:28 AM EDT> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '84' for queue: 'w eblogic.kernel.Default (self-tuning)' has been busy for "622" seconds working on the request "Http Request: /c sds/esignature/esigPopup.faces", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace: weblogic.jdbcx.base.BaseXAConnection.getXAResource(Unknown Source) weblogic.jdbc.wrapper.XAConnection.getXAResource(XAConnection.java:455) weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:693) weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:460) weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1455) weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1372) weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1362) weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:329) weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:294) weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:284) weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:466) weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:357) weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:83) weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1476) weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1274) weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:195) weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:70) weblogic.jdbc.wrapper.Statement.checkStatement(Statement.java:250) weblogic.jdbc.wrapper.Statement.doClose(Statement.java:342) weblogic.jdbc.wrapper.Statement.close(Statement.java:329) com.pfizer.disco.fw.DaoBase.queryMultipleRows(DaoBase.java:1303) Here is a snippet from the thread dump: "[ACTIVE] ExecuteThread: '397' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=10 tid=0x005340a8 nid=0x20f waiting for monitor entry [0x812ff000..0x812ffb10]
  3. 0

    Ant tasks

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: No suitable driver [schematool] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78) [schematool] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234) [schematool] at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT ask.java:46) [schematool] at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115) [schematool] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) [schematool]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Ant tasks

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: No suitable driver [schematool] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78) [schematool] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234) [schematool] at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT ask.java:46) [schematool] at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115) [schematool] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) [schematool]
  6. 0

    Ant tasks

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: No suitable driver [schematool] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:78) [schematool] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1234) [schematool] at com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolT ask.java:46) [schematool] at com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:115) [schematool] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166) [schematool]

    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

      The database is already in use by another process [java] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.<init>(SchemaTool.java:92) [java] at com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1070) [java] Full thread dump: [java] Full thread dump: "Thread-5" daemon prio=5 tid=0x8aacaf8 nid=0x6b4 runnable [0x8dcf000..0x8dcfdbc]

      at java.io.FileInputStream.readBytes()
    2. Java RT
      FileInputStream.read
      1. java.io.FileInputStream.readBytes(Native Method)
      2. java.io.FileInputStream.read(FileInputStream.java:161)
      2 frames
    3. Ant
      StreamPumper.run
      1. org.apache.tools.ant.taskdefs.StreamPumper.run(StreamPumper.java:99)
      1 frame
    4. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:479)
      1 frame