aspose file tools*
The moose likes JDBC and the fly likes OrionCMTConnection not closed, check your code! Logical connection not closed, check your code! Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "OrionCMTConnection not closed, check your code! Logical connection not closed, check your code!" Watch "OrionCMTConnection not closed, check your code! Logical connection not closed, check your code!" New topic
Author

OrionCMTConnection not closed, check your code! Logical connection not closed, check your code!

vipul bondugula
Ranch Hand

Joined: Oct 14, 2010
Posts: 218
Hi ,

OrionCMTConnection not closed, check your code! Logical connection not closed, check your code!
-Djdbc.connection.debug=true

i got a solution for this in java ranch..Thread tells me to set the -Djdbc.connection.debug=true in property.

what my doubt is, where should i set the property...
Please repond to this query...Urgent

Thanks in Advance..
vipul




Thanks
Vipul Kumar
vipul bondugula
Ranch Hand

Joined: Oct 14, 2010
Posts: 218
HI

Once again iam repeating my query..Please respond.

I am using JDeveloper 10g and oc4j server.
I am getting below message.


OrionCMTConnection not closed, check your code!

11/07/29 18:51:36 Logical connection not closed, check your code!

11/07/29 18:51:36 (Use -Djdbc.connection.debug=true to find out where the leaked connection was created)

I already read a thread in this forum that given me almost answer.I got the answer ,but the problem is iam unable to do that.

They told to "-Djdbc.connection.debug=true" keep this option for jvm.

I am not understanding , in jdeveloper where to configure this option



Please respond to this..I need it urgent..

Thanks & Regards,
Vipul

vipul bondugula
Ranch Hand

Joined: Oct 14, 2010
Posts: 218
Hi Everyone,

I successfully configured that for my application.
Right click on your project-->click on project properties-->Runner-->Java options.configure "-Djdbc.connection.debug=true"

Now whereever a connection is not closed you can see error mess on your console.

Thanks & Regards,
Vipul Reddy Bondugula.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: OrionCMTConnection not closed, check your code! Logical connection not closed, check your code!
 
Similar Threads
DriverManagerConnection PoolConnection Error
DriverManagerConnectionPool
Using DataSource with Oracle 10g Application Server results in error
Strange problem with IBATIS framework and OC4J container
OrionCMTConnection not closed, check your code! Logical connection not closed, check your code!