Maybe you should return the dbselector by releasing it after the work:
manager.release(dbselector);
And connection.close() should return the connection correctly into the pool. I'm not shure where I had read this but it is documented somewhere that this wrapps the java connection and returns the connection correctly into the pool.
Regards Stephan
Christoph Kliemt wrote:
Hi!
i am not sure if this is correct:
In an xsp-page:
<xsp:logic>
[...]
ComponentSelector dbselector =
(ComponentSelector) manager.lookup(DataSourceComponent.ROLE + "Selector");
datasource = (DataSourceComponent) dbselector.select("some_db");
Connection connection = datasource.getConnection();
Statement statement = connection.createStatement();
ResultSet rs = statement.executeQuery( some sql);
[...]
connection.close();
</xsp:logic>
If i dont close the connection cocoon hangs and waits for the pool. So there has to be a way to put the connction back into the pool. Is this done by closing the connection?
Where in the docs do i find this information?
cocoon version is 2.1.5.1
cu
christoph
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
