I think not. This is the first time I GET the connection, and it complains that I did
not close it. Also, according to my understanding, I do not have to explicitly close
pooled connections. At least, when we were using 1.0.3 the documentation said
something to that effect.
Thanx for responding, I thought I wasn't getting my message through.
Jaco
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Will Glozer
Sent: 09 October 2000 19:09
To: Orion-Interest
Subject: RE: LogicalDriverManagerXAConnection not closed
It means that you forgot to close the connection when you
were finished using it.
-----Original Message-----
From: Jaco van Rooijen [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 09, 2000 12:08 AM
To: Orion-Interest
Subject: RE: LogicalDriverManagerXAConnection not closed
Anybody have any ideas?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jaco van
Rooijen
Sent: 06 October 2000 13:40
To: Orion-Interest
Subject: LogicalDriverManagerXAConnection not closed
I am developing against the stable 1.3.8
I get an output stating:
LogicalDriverManagerXAConnection not closed, check your code!
Created at:
java.lang.Throwable: OrionCMTConnection created
at com.evermind.sql.ai.<init>(JAX)
at com.evermind.sql.OrionCMTDataSource.getConnection(JAX)
at
com.agri24.data.LegalEntityBean.getConnection(LegalEntityBean.java:843)
at
com.agri24.data.LegalEntityBean.ejbFindByAgri24ID(LegalEntityBean.java:463)
at
LegalEntityHome_EntityHomeWrapper55.findByAgri24ID(LegalEntityHome_EntityHom
eWrapper55.java:1122)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.bd.run(JAX)
at com.evermind.server.rmi.bb.hy(JAX)
at com.evermind.server.rmi.bb.run(JAX)
at com.evermind.util.f.run(JAX)
LegalEntityBean.java:843 says -
Connection newConn =
((javax.sql.DataSource)ctx.lookup("java:comp/env/jdbc/LegalEntityDataSource"
)).getConnection();
The call goes through, but the console has this exception on it. What does
that mean?
Regards
Jaco
