JDBC Connections not closed

Hi,
we work on a Jdevelopper intranet application and an Oc4j application server.
recently, we have reached the maximum number of connections to an Oracle DB.
apparently, we have a lot of old connections that are not closed!!
is there any action to do on Oc4j configuration or Jdevelopper application to avoid this problem ??
thank you for help.
Cordialy

Hi
did you find any solution for this problem? I'm having the same problem...
thanks in advanced
Vitor

Similar Messages

Jdbc Connections not closed on OC4J 9.0.4 - BUG VERSION?

Hi, I migrate my applications from 9ias 9.0.3 to OAS 10g with OC4J 9.0.4.
After migration, the jdbc connections provide by Data Source Names don't be closed in Oracle Database 8.1.7, stay INACTIVE state, and in few time of access, the Oracle Database exceded limit of sessions.
The OC4J 9.0.4.1 resolve this problem ? Where i can download this release ?
Any body have any idea ?
thanks,
Danilo

Hi
did you find any solution for this problem? I'm having the same problem...
thanks in advanced
Vitor

TopLink logical connection not closed

Hi everybody,
I have a problem when using db adapter for polling databases tables. This is using TopLink to access database's data.
My process was running w/o errors till I have started to use external data source defined in OAS.
My oc4j-ra.xml file contains:
============================================================
 <connector-factory location="eis/DB/TestData" connector-name="Database Adapter">
 <config-property name="driverClassName" value="oracle.jdbc.driver.OracleDriver"/>
 <config-property name="connectionString" value=""/>
 <config-property name="userName" value=""/>
 <config-property name="password" value=""/>
 <config-property name="minConnections" value="5"/>
 <config-property name="maxConnections" value="5"/>
 <config-property name="minReadConnections" value="1"/>
 <config-property name="maxReadConnections" value="1"/>
 <config-property name="usesExternalConnectionPooling" value="true"/>
 <config-property name="dataSourceName" value="jdbc/TESTDS"/>
 <config-property name="usesExternalTransactionController" value="true"/>
 <config-property name="platformClassName" value="oracle.toplink.internal.databaseaccess.Oracle9Platform"/>
 <config-property name="usesNativeSequencing" value="true"/>
 <config-property name="sequencePreallocationSize" value="50"/>
 <config-property name="tableQualifier" value=""/>
 <config-property name="defaultNChar" value="false"/>
 <config-property name="usesBatchWriting" value="true"/>
 </connector-factory>
============================================================
Once I have switched to this oc4j-ra.xml configuration file I got the following error in files logs (using the -Djdbc.connection.debug=true flag)
============================================================
06/09/25 11:40:46 OrionCMTConnection not closed, check your code!
06/09/25 11:40:46 Logical connection not closed, check your code!
06/09/25 11:40:46 Created at:
06/09/25 11:40:46 java.lang.Throwable: OrionCMTConnection created
06/09/25 11:40:46 at com.evermind.sql.OrionCMTConnection.<init>(OrionCMTConnection.java:121)
06/09/25 11:40:46 at com.evermind.sql.OrionCMTConnectionFinalize.<init>(OrionCMTConnectionFinalize.java:42)
06/09/25 11:40:46 at com.evermind.util.ClassOptimizerFactory.getOrionCMTConnection(ClassOptimizerFactory.java:80)
06/09/25 11:40:46 at com.evermind.sql.OrionCMTDataSource.getConnection(OrionCMTDataSource.java:237)
06/09/25 11:40:46 at com.evermind.sql.OrionCMTDataSource.getConnection(OrionCMTDataSource.java:227)
06/09/25 11:40:46 at oracle.toplink.jndi.JNDIConnector.connect(JNDIConnector.java:102)
06/09/25 11:40:46 at oracle.toplink.sessions.DatabaseLogin.connect(DatabaseLogin.java:218)
06/09/25 11:40:46 at oracle.toplink.internal.databaseaccess.DatabaseAccessor.reconnect(DatabaseAccessor.java:1323)
06/09/25 11:40:46 at oracle.toplink.internal.databaseaccess.DatabaseAccessor.incrementCallCount(DatabaseAccessor.java:1198)
06/09/25 11:40:46 at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:633)
06/09/25 11:40:46 at oracle.toplink.publicinterface.Session.executeCall(Session.java:793)
06/09/25 11:40:46 at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:131)
06/09/25 11:40:46 at oracle.toplink.internal.queryframework.CallQueryMechanism.executeCall(CallQueryMechanism.java:115)
06/09/25 11:40:46 at oracle.toplink.internal.queryframework.CallQueryMechanism.executeSelectCall(CallQueryMechanism.java:194)
06/09/25 11:40:46 at oracle.toplink.internal.queryframework.CallQueryMechanism.selectAllRows(CallQueryMechanism.java:565)
06/09/25 11:40:46 at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:733)
06/09/25 11:40:46 at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:708)
06/09/25 11:40:46 at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:447)
06/09/25 11:40:46 at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:493)
06/09/25 11:40:46 at oracle.toplink.queryframework.ReadQuery.execute(ReadQuery.java:125)
06/09/25 11:40:46 at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:1958)
06/09/25 11:40:46 at oracle.toplink.threetier.ClientSession.internalExecuteQuery(ClientSession.java:390)
06/09/25 11:40:46 at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1086)
06/09/25 11:40:46 at oracle.toplink.publicinterface.Session.executeQuery(Session.java:1038)
06/09/25 11:40:46 at oracle.toplink.publicinterface.Session.executeQuery(Session.java:876)
06/09/25 11:40:46 at oracle.tip.adapter.db.inbound.DestructivePollingStrategy.poll(DestructivePollingStrategy.java:211)
06/09/25 11:40:46 at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:247)
06/09/25 11:40:46 at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:213)
06/09/25 11:40:46 at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
06/09/25 11:40:46 at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
06/09/25 11:40:46 at java.lang.Thread.run(Thread.java:534)
============================================================
Any clue on this?
Thankfully,
amo

Thanks Marc,
I have finally noticed that was not related with some TopLink error.
So, is there any other way to refer in the DBAdapter to an OAS datasource?
Regards,
amo

Lot of cursors hanging even the jdbc connection are closed

We use tomcat and thin oracle driver for out application. But we found lot of cursors hanging even the jdbc connection are closed.
We use a connection pool to manage the connections.

after properly closing the connections ,try to set all the Connection objects and ResulSet objects to null (force to null) , most likely these inactive sessions will dissapear.
might be a java garbage collection issue?
anyhow. I managed to get most of these inactive sessions to disappear. although I am using a Servlet. some of them are still not closed
Regards

Database Connections Not Closing

I'm using iBatis for PostgreSQL database access and frequently have problems with connections not being closed. Here is a copy of my sqlMapConfig file:
============================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE sqlMapConfig
PUBLIC "-//iBATIS.com//DTD SQL Map Config 2.0//EN"
"http://www.ibatis.com/dtd/sql-map-config-2.dtd">
<sqlMapConfig>
<properties resource="ibatis.properties" />
<settings
lazyLoadingEnabled="true"
cacheModelsEnabled="true"
enhancementEnabled="false"
useStatementNamespaces="false"
/>
<transactionManager type="JDBC" commitRequired="true">
<dataSource type="DBCP">
<property name="driverClassName" value="${driver}" />
<property name="url" value="${url}" />
<property name="username" value="${username}" />
<property name="password" value="${password}" />
<property name="maxActive" value="10"/>
<property name="maxIdle" value="5"/>
<property name="maxWait" value="5000"/>
<property name="logAbandoned" value="true"/>
<property name="removeAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="1"/>
<property name="Driver.logUnclosedConnections" value="true"/>
</dataSource>
</transactionManager>
<sqlMap resource="job-sqlMap.xml" />
</sqlMapConfig>
============================
Due to the logAbandoned and removeAbandoned settings, I get a report in my log file whenever there is a connection that was not properly closed. Here is one of those log entries:
23:22:51.483 (10) Finalizing a Connection that was never closed:
java.lang.Throwable: Connection was created at this point:
at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:175)
at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:84)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.init(JdbcTransaction.java:48)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:89)
at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeQueryForList(MappedStatement.java:139)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:567)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:541)
at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(SqlMapSessionImpl.java:118)
at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.queryForList(SqlMapClientImpl.java:94)
at edu.calpoly.lib.multimedia.big.db.AutomaticPeriodUpdateIBatisImplDBHandler.getGamesWithAutomaticUpdatePolicy(AutomaticPeriodUpdateIBatisImplDBHandler.java:154)
at edu.calpoly.lib.multimedia.big.game.AutoUpdateThread.run(AutoUpdateThread.java:155)
The file: AutomaticPeriodUpdateIBatisImplDBHandler.java contains an iBatis call on line # 154:
--> list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
from the map file:
<select id="getGamesWithAutoPolicy" resultClass="java.util.HashMap">
<![CDATA[
SELECT gameid, policy
FROM update_policy
]]>
</select>
Here is the code for the entire method that uses this transaction:
============================
public List getGamesWithAutomaticUpdatePolicy() throws BIGDatabaseFacadeException
List list = new ArrayList();
try
sqlMap.startTransaction();
list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
sqlMap.commitTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
finally
try
sqlMap.endTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
return list;
============================
I know that this should be handled as an automatic transaction, but I tried adding the start, commit and end transaction commands in my desperate attempt to fix this problem (but it still didn't help).
Here is my code for creation of sqlMap -
--> sqlMap = SqlMapClientBuilder.buildSqlMapClient(Resources.getResourceAsReader("sqlMaps.xml"));
Except for the fact that occasionally connections are not closed, overall my database access using iBatis works very well.
In the course of trying to fix this problem I've worked to update all my lib files to the latest versions, and here is current status:
My iBatis lib file: ibatis-2.3.4.726.jar
My JDBC driver: postgresql-8.4-701.jdbc3.jar
Required commons files:
commons-dbcp-1.2.2.jar
commons-pool-1.5.3.jar
Note that I tried adding --> commitRequired="true" to the transactionManager in sqlMaps.xml, hoping it might help, but no joy.
Please help me figure out why my database connections often do not close. Thank you very much!

I'm sorry, but I don't understand what you mean by "close the session." I believe iBatis is supposed to take care of all that automatically. My understanding is that all the user does is create the sqlMapClient and then use it along with various map files to query and update the database. iBatis does the rest.

Connection not closed in the database server end

Hi,
Our database server (sql server 2000) and java application are running in two different boxes. Because the java application sent to the db server quite a few queries that can not be completed (applications hangs there) due to huge amount of data (18 million records in one table and 1 million records in another table and there are joins among the three tables), we stopped the java program. However, in the db server end, the connections associated with these problem queries were not closed although the java app end already closed these connections by calling connection.close(). When this happened, we have to manually close the connection from sql server enterprise manager.
Here are the questions.
1)what could be the reason why db server does not close the connection?
2)Is there any solution in the java end that could close the connection in the db server end when this situation happens? I say this situation happens, I mean in most cases when java application closes connection, db server closes connections in its end too.
Thanks
Mark

mark.lin wrote:
Thanks for your answers and questions.
Here are the answers to your questions
1)The jdbc driver is jturboJTurbo? Never heard of it. You mean this?
http://www.newatlanta.com/products/jturbo/index.jsp
Why pay for something when you have two options available that are free? One of them is from Microsoft itself. Whose idea was this?
2)It's a desk top application.
It seems to me that it should not be driver issue. I was this happened the Microsoft's own jdbc driver. By jdbc specification, although you don't close the connection explicitly in the program, the connection will be automatically closed in the java app end during garbage collection. Very bad - never depend on this. Always close your ResultSet, Statement, and Connection in reverse order of opening in a finally block, each one wrapped in individual try/catch blocks.
One should never, ever depend on the GC to take care of resources like database connections or resource handles. Those should be cleaned up by your code.
I tested this by intentionally not closing a connection. When I stops the application, the connection in the sql server end was also closed.
But if you don't close the application and fail to close connections, you can see where eventually you'll exhaust the pool.
It seems to me this is a sql server issue rather than a jdbc driver issue. I need way to prove this.
Like I suggested, it's easy to swap in the jTDS driver and try it again. What do you have to lose?
Or call Microsoft support and ask them. Or maybe JTurbo. You're paying for it - might as well use the support.
%

Database connection not closing on time out

Hi All,
Not sure if this is the right place for this question but..
I've moved my app (built using jdev10.1.2., adf bc's and jsp's) to an app server. For some reason, the database connection is not closing. I have 46 connections to the database and I''m the only one with the URL, not good.
So can anyone shed any light on this? I thought it should disconnect after a time out but its not.
Any ideas would be gratfully received.
Thanks in advance

or try this one..
Go to the bottom of the tutorial, you will find the configuration...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bc9baf90-0201-0010-479a-b49b25598ebf

JDBC Connections not being returned to pool

Greetings All.
I really need some help here to find out where my connections are being held.
I have a transactional connection pool that runs out of connections on average three times a day. I've read all the threads in the newsgroups for connection leaks and how to always release connections in the finally block.
1.
I can confirm that it's definitely not a connection leak, I confirmed this by using the jar for tracing connection leaks and none was displayed.
2.
I've looked at all our code and all code that uses jdbc connections destroys jdbc resources in the finally clause.
3.
I'm new to the department and therefore cannot tell you what new code was put in that caused this problem to occur.
4.
We're using WL 8.1.3 AND JDK 1.4.2_06
5.
I've tried JMX to view what the connections are doing when this problem occurs, and hence enabled statement cache which revealed nothing of interest to me. I just wish somehow I could get to trace which threads reserved the connections and do a stack trace on them.
The most frequent error in my jdbc logs is :
java.sql.SQLException: ORA-01401: inserted value too large for column
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
     at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
     at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:656)
     at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:70)
     at net.cellc.sal.ejb.saldataaccess.TransactionDAO.updateRecordStatus(TransactionDAO.java:76)
     at net.cellc.sol.ejb.sol.SOLBean.updateRecord(SOLBean.java:312)
     at net.cellc.sol.ejb.sol.SOLBean.processMessage(SOLBean.java:170)
     at net.cellc.sol.ejb.sol.SOL_ytyu34_EOImpl.processMessage(SOL_ytyu34_EOImpl.java:46)
     at net.cellc.sal.ejb.sal.SALBean.callSOL(SALBean.java:339)
     at net.cellc.sal.ejb.sal.SALBean.process(SALBean.java:201)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl.process(SAL_ki83rk_EOImpl.java:100)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
SQLException: SQLState(23000) vendor code(1401)
Your help would be really appreciated.
Regards
Ze Casperian

Hi. Show us your pool definition. You should turn off refresh test minutes.
Set it to 9999999.
Joe
Mncedisi Kasper wrote:
Greetings All.
I really need some help here to find out where my connections are being held.
I have a transactional connection pool that runs out of connections on average three times a day. I've read all the threads in the newsgroups for connection leaks and how to always release connections in the finally block.
1.
I can confirm that it's definitely not a connection leak, I confirmed this by using the jar for tracing connection leaks and none was displayed.
2.
I've looked at all our code and all code that uses jdbc connections destroys jdbc resources in the finally clause.
3.
I'm new to the department and therefore cannot tell you what new code was put in that caused this problem to occur.
4.
We're using WL 8.1.3 AND JDK 1.4.2_06
5.
I've tried JMX to view what the connections are doing when this problem occurs, and hence enabled statement cache which revealed nothing of interest to me. I just wish somehow I could get to trace which threads reserved the connections and do a stack trace on them.
The most frequent error in my jdbc logs is :
java.sql.SQLException: ORA-01401: inserted value too large for column
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)
     at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047)
     at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
     at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:656)
     at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:70)
     at net.cellc.sal.ejb.saldataaccess.TransactionDAO.updateRecordStatus(TransactionDAO.java:76)
     at net.cellc.sol.ejb.sol.SOLBean.updateRecord(SOLBean.java:312)
     at net.cellc.sol.ejb.sol.SOLBean.processMessage(SOLBean.java:170)
     at net.cellc.sol.ejb.sol.SOL_ytyu34_EOImpl.processMessage(SOL_ytyu34_EOImpl.java:46)
     at net.cellc.sal.ejb.sal.SALBean.callSOL(SALBean.java:339)
     at net.cellc.sal.ejb.sal.SALBean.process(SALBean.java:201)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl.process(SAL_ki83rk_EOImpl.java:100)
     at net.cellc.sal.ejb.sal.SAL_ki83rk_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
SQLException: SQLState(23000) vendor code(1401)
Your help would be really appreciated.
Regards
Ze Casperian

Generic JDBC connection not setting up.

Hey ..
I am trying to make a Generic JDBC connection in DB adapter. For the steps I am refering to this blog: https://blogs.oracle.com/middleware/entry/configuring_mssql_with_soa_suite
so I went as follows: step 3 of 4 of adapter configuration > create new connection > Driver class: new > Library: Browse
chose the driver source .jar, put the correct URL & tested the connection.
The Error that came said:
"Test failed: Driver class not found.
Verify the Driver location"
I tried same thing with sqljdbc.jar - the file used in the blog ... Same error was there.
What's the mistake? What should I try to do?

The problem got solved ..
Actually the path was correct but the driver class name was wrong ..
Perhaps it tries to find the driver class with the specific name in specified .jar
I thought we are CREATING new thing ..
Thanks anyways for your help

CR4E only support JDBC connections not support exterior datasource?

The current vision only support JDBC connections?when I organized the datasource or datalist in the application, if this datasource or datalist can connect the data connection? Thank you!jessica

 Hi JessicaYes, the JRC only works with JDBC connections. You can also pass it POJOs at runtime. Rob Horne <a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a>

Database connection not closed in Destroy() method of servlet

Hi,
I have a problem with my deployed web application. At first, I thought Glassfish was messing up on me, and after checking the log I could see plenty of null pointer exceptions being thrown at lines in my code where I generate prepared statements from my connection object. I have been initialising my connection in the Init() method of all my classes, and equally, I've been closing it in Destroy(). I can only imagine that destroy() isn't being called - since the log clearly shows "connection success" messages but not "connection closed" messages. I am connecting to the servlets via a J2ME app on my mobile phone. Does connecting in this way somehow not invoke the destroy method when the servlets work is complete? Am I going to need to move all my connection initilisation and closing into the necessary doGet/doPost methods of each of my servlets?
Chris

You shouldn't be keeping the connection that long open. It's a bad design. It will timeout sooner or later and your complete application will crash. Always acquire and close the connection in the shortest possible scope, preferably just in the same method block where you process the query and/or results. If you want to improve performance while connecting, consider using a connection pool.
Back to the actual problem: a servlet is created only once during application's lifetime and not during every request as you appears to think.
You may find this tutorial useful to read on about using the DAO pattern in JSP/Servlet.
[http://balusc.blogspot.com/2008/07/dao-tutorial-use-in-jspservlet.html]

OrionCMTConnection not closed, check your code. OrionCMTConnection created

Hi everybody, I have an application running in OAS 10g, this application generally works fine, but in the opmn log of my instance in found the next message :
07/01/09 17:01:56 OrionCMTConnection not closed, check your code!
07/01/09 17:01:56 Logical connection not closed, check your code!
07/01/09 17:01:56 Created at:
07/01/09 17:01:56 java.lang.Throwable: OrionCMTConnection created
07/01/09 17:01:56 at com.evermind.sql.OrionCMTConnection.<init>(OrionCMTConnection.java:121)
07/01/09 17:01:56 at com.evermind.sql.OrionCMTConnectionFinalize.<init>(OrionCMTConnectionFinalize.java:42)
07/01/09 17:01:56 at com.evermind.util.ClassOptimizerFactory.getOrionCMTConnection(ClassOptimizerFactory.java:80)
07/01/09 17:01:56 at com.evermind.sql.OrionCMTDataSource.getConnection(OrionCMTDataSource.java:237)
07/01/09 17:01:56 at com.evermind.sql.OrionCMTDataSource.getConnection(OrionCMTDataSource.java:217)
07/01/09 17:01:56 at view.base_control_maq.consulta_t_orden_produccion_cod(base_control_maq.java:1934)
07/01/09 17:01:56 at control_maq._detalle__control__actividad._jspService(_detalle__control__actividad.java:280)
07/01/09 17:01:56 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
07/01/09 17:01:56 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
07/01/09 17:01:56 at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
07/01/09 17:01:56 at org.apache.struts.tiles.TilesUtilImpl.doInclude(TilesUtilImpl.java:99)
07/01/09 17:01:56 at org.apache.struts.tiles.TilesUtil.doInclude(TilesUtil.java:135)
07/01/09 17:01:56 at org.apache.struts.taglib.tiles.InsertTag.doInclude(InsertTag.java:760)
07/01/09 17:01:56 at org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:892)
07/01/09 17:01:56 at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:462)
07/01/09 17:01:56 at templetas.template._jspService(_template.java:68)
07/01/09 17:01:56 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
07/01/09 17:01:56 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
07/01/09 17:01:56 at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
07/01/09 17:01:56 at org.apache.struts.tiles.TilesUtilImpl.doInclude(TilesUtilImpl.java:99)
07/01/09 17:01:56 at org.apache.struts.tiles.TilesUtil.doInclude(TilesUtil.java:135)
07/01/09 17:01:56 at org.apache.struts.taglib.tiles.InsertTag.doInclude(InsertTag.java:760)
07/01/09 17:01:56 at org.apache.struts.taglib.tiles.InsertTag$InsertHandler.doEndTag(InsertTag.java:892)
07/01/09 17:01:56 at org.apache.struts.taglib.tiles.InsertTag.doEndTag(InsertTag.java:462)
07/01/09 17:01:56 at control_maq._control__actividad._jspService(_control__actividad.java:125)
07/01/09 17:01:56 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
07/01/09 17:01:56 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
07/01/09 17:01:56 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
07/01/09 17:01:56 at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1063)
07/01/09 17:01:56 at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:263)
07/01/09 17:01:56 at org.apache.struts.action.RequestProcessor.internalModuleRelativeForward(RequestProcessor.java:1001)
07/01/09 17:01:56 at org.apache.struts.tiles.TilesRequestProcessor.internalModuleRelativeForward(TilesRequestProcessor.java:345)
07/01/09 17:01:56 at org.apache.struts.action.RequestProcessor.processForward(RequestProcessor.java:560)
07/01/09 17:01:56 at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:209)
07/01/09 17:01:56 at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1194)
07/01/09 17:01:56 at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
07/01/09 17:01:56 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
07/01/09 17:01:56 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
07/01/09 17:01:56 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
07/01/09 17:01:56 at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:239)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
07/01/09 17:01:56 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
07/01/09 17:01:56 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
07/01/09 17:01:56 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
07/01/09 17:01:56 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
07/01/09 17:01:56 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
07/01/09 17:01:56 at java.lang.Thread.run(Thread.java:534)
This error occurred with other java files too, but in the code apparently the jdbc connections are closed. I'm searching since a week the problem and different solutions in the forum but this does not apply for my problem, please help me.
Regards
Jeanette.

Thanks Frances, but I set -Ddatasource.verbose=true and get some like this:
Releasing connection com.evermind.sql.DriverManagerXAConnection@1cf6046 to pool (Pool size: 5)
com.evermind.sql.OrionCMTDataSource@1a9a15f: Cache timeout, closing connection (Pool size: 4)
com.evermind.sql.OrionCMTDataSource@1a9a15f: Cache timeout, closing connection (Pool size: 3)
com.evermind.sql.OrionCMTDataSource@1a9a15f: Cache timeout, closing connection (Pool size: 2)
com.evermind.sql.OrionCMTDataSource@1a9a15f: Cache timeout, closing connection (Pool size: 1)
null: Releasing connection com.evermind.sql.DriverManagerXAConnection@6409e1 to pool (Pool size: 1)
I suppose that some connections were closed well and others didn't close in the right form and use cache timeout.
Nevertheless even now I don’t know how to correct the message of connection:
07/01/11 18:31:44 OrionCMTConnection not closed, check your code!
07/01/11 18:31:44 Logical connection not closed, check your code!
07/01/11 18:31:44 Created at:
07/01/11 18:31:44 java.lang.Throwable: OrionCMTConnection created
07/01/11 18:31:44 at com.evermind.sql.OrionCMTConnection.<init>(OrionCMTConnection.java:121)
07/01/11 18:31:44 at com.evermind.sql.OrionCMTConnectionFinalize.<init>(OrionCMTConnectionFinalize.java:42).........
This time in the log I found other lines before the OrionCMTConnection….:
null: Releasing connection com.evermind.sql.DriverManagerXAConnection@d35cb2 to pool (Pool size: 1)
INFO - GenericFilterBean.init(118) | Initializing filter 'hibernateFilter'
INFO - GenericFilterBean.init(143) | Filter 'hibernateFilter' configured successfully
INFO - AbstractBeanFactory.getBean(219) | Creating shared instance of singleton bean 'sessionFactory'
INFO - AbstractBeanFactory.getBean(219) | Creating shared instance of singleton bean 'sessionFactory'
INFO - AbstractBeanFactory.getBean(219) | Creating shared instance of singleton bean 'dataSource'
INFO - AbstractBeanFactory.getBean(219) | Creating shared instance of singleton bean 'dataSource'
INFO - Environment.<clinit>(464) | Hibernate 3.0.5
INFO - Environment.<clinit>(477) | hibernate.properties not found
INFO - Environment.<clinit>(510) | using CGLIB reflection optimizer
INFO - Environment.<clinit>(540) | using JDK 1.4 java.sql.Timestamp handling
I'm totally disoriented now.. please help me
Jane.

Connections not being released from jdbc pool on WLS 5.1 sp8

I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin jdbc driver as shown in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com

Hi Caren,
Weblogic doesn't close connections on "time-out". There are some reasons
for this. The most important one is that even if you have such a
functionality,
in case of a connection leak all the available connections can be trashed in
a matter of milliseconds, so it wouldn't help at all. Though, weblogic does
close leaked connection when they are garbage collected, but it's easy to
see
that it doesn't help a lot, too.
So you need to make sure that all the JDBC objects are closed properly,
for example like in this code:
try {
} finally {
try {resultSet.close();} catch (SQLException se) {}
try {preparedStatement.close();} catch (SQLException se) {}
try {connection.close();} catch (SQLException se) {}
Also it's possible that you simply don't have enough connection.
You could try to increase size of the pool.
Regards,
Slava Imeshev
"Karen Law" <[email protected]> wrote in message
news:[email protected]...
Closing the DB connections is important. But is there any parameters to be
set in the WebLogic configuration in order to release the connection whenit
hasn't been closed for a long time? Say, setting the connection timeout?
Many thx!
Karen
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Do you close the DB connections in a finally block after you've finished
using them?
If not your application is leaking the connections and sometimes GC is
not able or does not free those in a timely manner.
--dejan
Anish Srivastava wrote:
I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin jdbc driver as
shown
in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com

BI Publisher not closing connection pool connections?

Hi:
I'm using Oracle WLS 10.3.3, BIP 10.1.3.4.1.
I have reports that were using JDBC data sources defined in BIP and I can run them all day with no problems. I created a JDBC connection pool in the WLS, created a JNDI name for it and then got BIP to recognize the JNDI data source. Finally, I modified the report data template to use the JNDI data source. It all works -- for a time. But after 20 or so executions I get an error that there are no more resources (connections). I went into the WLS and configured "inactive connection timeout" to 15 seconds or so. This eventually gives me another connection but doesn't prevent the lock-up.
Why are the connections no being re-used? I am the only user, it should be using a connection, putting it back into the pool, and then re-using that still open connection for my next query. Is there another setting I need to set in WLS? Do I need to somehow tell the report to close the connection? I wouldn't think the transaction mode for the connection matters, but I could set that as well if I need to.
Thanks.

the reason, i asked you to upgrade the BIP patch
DB CONNECTION IS NOT PROPERLY CLOSED,
BI PUBLISHER NOT CLOSING DB CONNECTIONS USED FOR 'LIST OF VALUES' PARAMETERS
there are few fixes related to Db connection in latest patch.
you can get the latest 10.1.3.4.1 patch for just BIP alone, not OBIEE
I would suggest you to log an SR and prove it to Support.
their first suggestion wud be like mine ;)

Accidentally abandoned and not closed connections

Tome cat datasource can close abandoned connections. can weblogic data source implement
this? If not how can webligic connection pool deal with these accidentally abandoned
and not closed connections?

zorro wrote:
connection is retrived by this function.
public Connection createConnection()throws Exception{
try{
InitialContext ictx=new InitialContext();
DataSource ds=(DataSource)ictx.lookup("jdbc/Oracle");
return ds.getConnection();
catch(NamingException e){
logger.error("failed to get connection:"+e);
return null;
And most of us use it in the way as follow. But I am not sure that there is no
connection leak in the code of the other programmers. If connection leak steadily
and seldom occur, what will happan when the weblogic server works for a long time?
I know that tomcat datasource handal the connection leak very well.The code below is correct. As soon as GC finds an abandoned connection, it will
be closed and returned to the pool. You can also turn on leak checking, which will
print out where the leaked connection was reserved, to help you find the code tp fix.
Joe
>
>
Connection conn=null;
try{
conn=createConnection();
catch(Exception e ){
finally{
try{
if(conn!=null)conn.close();
catch(Exception e ){}

JDBC Connections not closed

Similar Messages

Maybe you are looking for