|
| Re: JDBC connection release every 30 seconds |
 |
Tue, 6 May 2008 09:55:11 -0700 |
Sandeep Gautam wrote:
> > Hi,
> >
> > Every 30 seconds weblogic forcibly releases a JDBC
> > connection on one of our 3 managed servers. The
> > stacktrace is pasted below.
> >
> > The process thats holding the connection seems to be
> > a Exception, and the stacktrace seems to come from
> > within Weblogic (9.1).
> >
> > Does anybody have ideas where I could start looking
> > for the reason?
> >
> > <Nov 15, 2007 11:28:01 AM CET> <Warning> <JDBC>
> > <BEA-001153>
> > <Forcibly releasing inactive connection
"[weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_or
acle_jdbc_driver_LogicalConnection-SVDepot_qa2-6408,
oracle.jdbc.driver.LogicalConnection@12e28eb]" back into the connection
pool "SVDepot_qa2", currently reserved by: java.lang.Exception
> > at
> > at
> > at
> > at
> > weblogic.jdbc.common.internal.ConnectionEnv.setup(Conn
> > ectionEnv.java:291)
> > at
> > at
> > at
> > at
> > weblogic.common.resourcepool.ResourcePoolImpl.reserveR
> > esource(ResourcePoolImpl.java:307)
> > at
> > at
> > at
> > at
> > weblogic.common.resourcepool.ResourcePoolImpl.reserveR
> > esource(ResourcePoolImpl.java:285)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.common.internal.ConnectionPool.reserve(C
> > onnectionPool.java:455)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.common.internal.ConnectionPool.reserve(C
> > onnectionPool.java:346)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.common.internal.ConnectionPoolManager.re
> > serve(ConnectionPoolManager.java:83)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(D
> > ataSource.java:1460)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(Da
> > taSource.java:1288)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.jta.DataSource.getConnection(DataSource.
> > java:436)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.jta.DataSource.connect(DataSource.java:3
> > 92)
> > at
> > at
> > at
> > at
> > weblogic.jdbc.common.internal.RmiDataSource.getConnect
> > ion(RmiDataSource.java:359)
> > at
> > at
> > at
> > at
> > weblogic.store.io.jdbc.ReservedConnection.createConnec
> > tion(ReservedConnection.java:131)
> > at
> > at
> > at
> > at
> > weblogic.store.io.jdbc.ReservedConnection.resetConnect
> > ion(ReservedConnection.java:311)
> > at
> > at
> > at
> > at
> > weblogic.store.io.jdbc.ReservedConnection.testConnecti
> > on(ReservedConnection.java:293)
> > at
> > at
> > at
> > at
> > weblogic.store.io.jdbc.ReservedConnection.lock(Reserve
> > dConnection.java:260)
> > at
> > at
> > at
> > at
> > weblogic.store.io.jdbc.ReservedConnection.timerExpired
> > (ReservedConnection.java:432)
> > at
> > at
> > at
> > at
> > weblogic.timers.internal.TimerImpl.run(TimerImpl.java:
> > 259)
> > at
> > at
> > at
> > at
> > weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.ru
> > n(ServerWorkManagerImpl.java:518)
> > at
> > at
> > at
> > at
> > weblogic.work.ExecuteThread.execute(ExecuteThread.java
> > :207)
> > at
> > at
> > at
> > at
> > weblogic.work.ExecuteThread.run(ExecuteThread.java:179
> > )
> > .>
>
> hi,
> Even i m facing some issue with the Datasource
> once i create Datasource it is giving me following exception
> Please help
>
> [pre]
> <May 6, 2008 6:41:12 PM GMT+05:30> <Error> <WLI>
<000000> <Error occurred while
> polling for new rows in the Database
> java.sql.SQLException: Internal error: Cannot obtain XAConnection
weblogic.commo
> n.resourcepool.ResourceDisabledException: Pool CHINA_DS is disabled, cannot
allo
> cate resources to applications..
> at
weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1
> 325)
> at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:441)
> at weblogic.jdbc.jta.DataSource.connect(DataSource.java:397)
> at
weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSour
> ce.java:359)
> at
com.bea.wli.mbconnector.rdbms.trigger.RDBMSConnMDB.findRangeAndSubRan
> ges(RDBMSConnMDB.java:470)
> Truncated. see log file for complete stacktrace
>
>
> [/pre]
>
> Thanks in advance
> Sandeep
Hi. Your issue is different from the original topic of this
thread. The message is telling you that something bad happened
that caused the JDBC connection pool 'CHINA_DS' to lose
contact with the DBMS. Until the pool can re-connect, it
|
| Post Reply
|
|
|
|
|
|
|
|
|
|