cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan L├╝ttringhaus-Kappel <ste...@informatik.uni-bonn.de>
Subject Re: [C2] esql problem: pooling fails
Date Mon, 12 Feb 2001 10:33:12 GMT
On Sun, 11 Feb 2001, Berin Loritsch wrote:

> The connections are given back to the pool behind the scenes.  The design
> constraint of the
> Avalon DataSources is that they behave like the JDBC javax.sql.DataSource
> Interface.

I thinks it's really closing the java.sql.Connection, file is attached:

...
import java.sql.Connection;
...
  class EsqlConnection {

    DataSourceComponent datasource = null;

    Connection connection = null;
    String dburl = null;
    String username = null;
    String password = null;
  }
...
    EsqlConnection _esql_connection = null;
...
                _esql_connection.connection.close();
...

>
> Check the WEB-INF/logs/cocoon.log function--if you are using DEBUG level
> logging,
> you should see that the Connection is requested from Cocoon, and then
> returned to
> Cocoon.  If there is something else happening, then please let me know.

So I do (grep'ed for DEBUG and connection):

DEBUG   76947   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   19180   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   19773   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   49145   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   49960   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   50045   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection object created
DEBUG   50045   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   50120   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection object created
DEBUG   50120   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   50190   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection object created
DEBUG   50190   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   50266   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection object created
DEBUG   50266   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.
DEBUG   50339   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection object created
DEBUG   50339   [cocoon  ] (HttpProcessor[8080][4]): JdbcConnection 'jdbc:mysql://gondolin.informatik.uni-bonn.de/experiment'
has been requested from pool.


So it uses the up the 5 initial connection, makes another 5, and game over.
It never returns any, I read the whole logfile. Moreover, I don't think the
appropriate method is anywhere in the generated code?

Best regards,
Stefan L├╝ttringhaus-Kappel

Mime
View raw message