Use the source, Luke!
I know Marc and Rickard made some changes so that Minerva would
use the jBoss logger - perhaps this is causing the problem as it may
generate exceptions if run outside?
Anyway, what I suggest you do is put a
Thread.currentThread().dumpStack() in
org.jboss.minerva.factories.JDBCConnectionFactory.deleteObject so you can
see if the connections are really being permanently closed. If that
doesn't get hit, then you just have a bad wrapper (the real connection is
still open, but the wrapper around that is not getting recycled) and we'll
pursue that separately.
FYI, I'm planning to put together a separate Minerva JAR with all
the jBoss dependencies removed in the next week or so.
Aaron
On Tue, 14 Nov 2000, Bill Pfeiffer wrote:
> I have used the Minerva classes (jboss.jar) to do connection pooling
> in my Tomcat app, outside of the scope of jBoss. As of jBoss pr3, I
> was able to create a JDBCPoolDataSource, get connections from it, use
> and then close the connections. All was well.
>
> As of the jBoss pr4 and on up, the connections seem to be handed off
> from JDBCPoolDataSource as closed. IOW, when I get a connection from
> JDBCPoolDataSource, the connection is closed and any attempt to use
> the connection throws an exception.
>
> I am just doing a normal close on the connection. My assumption was
> that this just returned the connection to the pool. Is this not what
> is happening? How should I release a connection obtained by
> JDBCPoolDataSource?
>
> Note that I am not actually running jboss in this scenario, just using
> the Minerva classes from the jboss.jar.
>
> TIA for any help,
>
> Bill Pfeiffer
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
