javax.resource.ResourceException: Could not create connection

Stack Overflow | Karthik Kumar | 2 months ago
  1. 0

    Exception enclosed; code enclosed; please help. DB2 DB connectivity issue

    Oracle Community | 1 decade ago | 807598
    java.sql.SQLException: [BEA][DB2 JDBC Driver]Bind process is not active. Please ensure that the user has permissions to create packages. Packages cannot be created in an XA Connection.
  2. 0

    connection problem with as400 after upgrade to 2.5.2

    Oracle Community | 1 decade ago | 3004
    java.sql.SQLException: [SQL0204] SYSTABLES in SYSIBM type *FILE not found. You can resolve this issue by creating an extension of the DB2Dictionary that looks something like this: public class AS400Dictionary extends com.solarmetric.kodo.impl.jdbc.schema.dict.DB2Dictionary { public AS400Dictionary () { setValidateConnectionSQL ("some SELECT that is fast and valid"); } } The validate SQL is used from time to time when borrowing items from the connection pool to ensure that a connection is really alive, since the Connection.isClosed() method is notoriously bad at truly identifying live connections. -Patrick On Mon, 14 Jul 2003 10:54:05 +0000, Harald wrote: Hello, I was using kodo 2.4.2 with with an as400 db2 database (DB2 for OS/400 JDBC Driver). This worked fine for me. After upgrading to to kodo 2.5.2 i get the following exception: A connection could not be obtained in the specified login time of 30 seconds. [code=0;state=null] NestedThrowables: com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper: [SQL=SELECT .... A connection could not be obtained in the specified login time of 30 seconds.
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 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]
  5. 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..> Hi. What version of the Oracle DBMS are you running? Is it a supported version? Something is going wrong between the driver and the DBMS. Is there any info in the DBMS error log to indicate that/why it may have killed some running sessions? We may want you to reproduce this in a single-server case (easier to debug), with the driver spy logging turned on. Joe > 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]

    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

      [XQuery][DB2 JDBC Driver]Bind process is not active. Please ensure that the user has permissions to create packages. Packages cannot be created in an XA Connection.

      at com.ddtek.xquery.jdbc.db2base.ddcp.b()
    2. com.ddtek.xquery
      BaseDriver.connect
      1. com.ddtek.xquery.jdbc.db2base.ddcp.b(Unknown Source)[xqdb2.jar:]
      2. com.ddtek.xquery.jdbc.db2base.ddcp.a(Unknown Source)[xqdb2.jar:]
      3. com.ddtek.xquery.jdbc.db2base.ddco.b(Unknown Source)[xqdb2.jar:]
      4. com.ddtek.xquery.jdbc.db2base.ddco.a(Unknown Source)[xqdb2.jar:]
      5. com.ddtek.xquery.jdbc.db2.drda.ddb.a(Unknown Source)[xqdb2.jar:]
      6. com.ddtek.xquery.jdbc.db2.drda.ddp.b(Unknown Source)[xqdb2.jar:]
      7. com.ddtek.xquery.jdbc.db2.ddj.e(Unknown Source)[xqdb2.jar:]
      8. com.ddtek.xquery.jdbc.db2.ddj.a(Unknown Source)[xqdb2.jar:]
      9. com.ddtek.xquery.jdbc.db2.DB2ImplConnection.d(Unknown Source)[xqdb2.jar:]
      10. com.ddtek.xquery.jdbc.db2base.BaseConnection.b(Unknown Source)[xqdb2.jar:]
      11. com.ddtek.xquery.jdbc.db2base.BaseConnection.k(Unknown Source)[xqdb2.jar:]
      12. com.ddtek.xquery.jdbc.db2base.BaseConnection.b(Unknown Source)[xqdb2.jar:]
      13. com.ddtek.xquery.jdbc.db2base.BaseConnection.a(Unknown Source)[xqdb2.jar:]
      14. com.ddtek.xquery.jdbc.db2base.BaseDriver.connect(Unknown Source)[xqdb2.jar:]
      14 frames
    3. Java RT
      DriverManager.getConnection
      1. java.sql.DriverManager.getConnection(DriverManager.java:571)[rt.jar:1.7.0_51]
      2. java.sql.DriverManager.getConnection(DriverManager.java:215)[rt.jar:1.7.0_51]
      2 frames
    4. com.ddtek.xquery
      MediatorConnection.connect
      1. com.ddtek.xquery.extractor.ExtractorDataSource.createJDBCConnection(ExtractorDataSource.java:257)[ddxq.jar:]
      2. com.ddtek.xquery.extractor.ExtractorDataSource.getConnection(ExtractorDataSource.java:120)[ddxq.jar:]
      3. com.ddtek.xquery.mediator.SqlAdapter.connect(SqlAdapter.java:68)[ddxq.jar:]
      4. com.ddtek.xquery.mediator.MediatorConnection.connect(MediatorConnection.java:85)[ddxq.jar:]
      4 frames
    5. com.ddtek.xquery3
      XQueryDriver.connect
      1. com.ddtek.xquery3.xqj.DDXQConnection.<init>(DDXQConnection.java:81)[ddxq.jar:]
      2. com.ddtek.xquery3.xqj.DDXQDataSource._getConnection(DDXQDataSource.java:1528)[ddxq.jar:]
      3. com.ddtek.xquery3.xqj.DDXQDataSource.getConnection(DDXQDataSource.java:883)[ddxq.jar:]
      4. com.ddtek.xquery3.jdbc.XQueryDriver.connect(XQueryDriver.java:152)[ddxq.jar:]
      4 frames
    6. IronJacamar
      LocalManagedConnectionFactory.getLocalManagedConnection
      1. org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:260)[ironjacamar-jdbc.jar:1.0.23.1.Final-redhat-1]
      1 frame
    7. IronJacamar
      AbstractConnectionManager.allocateConnection
      1. org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:344)
      2. org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:404)
      3. org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:372)
      4. org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:364)
      5. org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368)
      6. org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
      6 frames
    8. IronJacamar
      WrapperDataSource.getConnection
      1. org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:139)[ironjacamar-jdbc.jar:1.0.23.1.Final-redhat-1]
      1 frame
    9. com.amex.common
      ConnectionFactory.createJNDIConnection
      1. com.amex.common.dataaccess.ConnectionFactory.createJNDIConnection(ConnectionFactory.java:117)[AmexCommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      1 frame
    10. com.amex.dce
      XMLJNDIConnectionType.getConnection
      1. com.amex.dce.common.dataaccess.XMLJNDIConnectionType.getConnection(XMLJNDIConnectionType.java:35)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      1 frame
    11. com.amex.common
      AbstractAmexConnectionType.getConnection
      1. com.amex.common.dataaccess.AbstractAmexConnectionType.getConnection(AbstractAmexConnectionType.java:20)[AmexCommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      1 frame
    12. com.amex.dce
      DataDirectXQueryDAO.writeXQueryResultsToFile
      1. com.amex.dce.common.dataaccess.xquery.XMLJNDIConnection.getConnection(XMLJNDIConnection.java:54)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      2. com.amex.dce.common.dataaccess.xquery.XMLJNDIConnection.openConnection(XMLJNDIConnection.java:38)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      3. com.amex.dce.common.dataaccess.xquery.XMLJNDIConnection.getXQConnection(XMLJNDIConnection.java:30)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      4. com.amex.dce.common.dataaccess.xquery.AbstractDDXQConnection.getPreparedExpressionWithBinding(AbstractDDXQConnection.java:56)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      5. com.amex.dce.common.dataaccess.xquery.DataDirectXQueryFileStreamer.streamToFile(DataDirectXQueryFileStreamer.java:105)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      6. com.amex.dce.common.dataaccess.xquery.DataDirectXQueryFileStreamer.streamXQueryToFile(DataDirectXQueryFileStreamer.java:48)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      7. com.amex.dce.common.dataaccess.xquery.DataDirectXQueryDAO.writeXQueryResultsToFile(DataDirectXQueryDAO.java:87)[DCECommon-1.0-SNAPSHOT.jar:1.0-SNAPSHOT]
      7 frames
    13. com.amex.matic
      DCEItemPreparer.execute
      1. com.amex.matic.dce.CatalogBuilder.prepareCatalogFile(CatalogBuilder.java:126)[classes:]
      2. com.amex.matic.dce.CatalogBuilder.buildCatalog(CatalogBuilder.java:77)[classes:]
      3. com.amex.matic.dce.Catalog.build(Catalog.java:55)[classes:]
      4. com.amex.matic.dce.Catalog.<init>(Catalog.java:33)[classes:]
      5. com.amex.matic.dce.DCEItemPreparer.getCatalog(DCEItemPreparer.java:239)[classes:]
      6. com.amex.matic.dce.DCEItemPreparer.buildAndUploadItem(DCEItemPreparer.java:197)[classes:]
      7. com.amex.matic.dce.DCEItemPreparer.handleRosterItem(DCEItemPreparer.java:168)[classes:]
      8. com.amex.matic.dce.DCEItemPreparer.prepareItems(DCEItemPreparer.java:88)[classes:]
      9. com.amex.matic.dce.DCEItemPreparer.execute(DCEItemPreparer.java:59)[classes:]
      10. com.amex.matic.dce.DCEItemPreparer.prepareItems(DCEItemPreparer.java:88)[classes:]
      11. com.amex.matic.dce.DCEItemPreparer.execute(DCEItemPreparer.java:59)[classes:]
      11 frames
    14. quartz
      SimpleThreadPool$WorkerThread.run
      1. org.quartz.core.JobRunShell.run(JobRunShell.java:202)[quartz-2.2.1.jar:]
      2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)[quartz-2.2.1.jar:]
      2 frames