Announcement

**alibaba2** · 24 May 2012, 03:45

I did not surrender.

Now: I don't use configuration in server.properties.
Admin Console showed me that I can use explicit JNDI connection name in "dbName" datasource parameter.

So now I have:

Code:

<DataSource
    ID="dsdb_sqlKlienci"
    serverType="sql"
    tableName="Klient"
    autoDeriveSchema="true"
dbName="java:comp/env/jdbc/sql_db"
>

<fields>
  <field name="KlientID" primaryKey="true" type="int"/>
</fields>

</DataSource>

And it works. Connections are allocated but slq datasource seems to not return connections to jndi pool. It takes a few (6-7 ?) conenctions and uses them in its own pool fo a few minutes. Then it releases it to the jndi pool.

* So now question: how to turn this off? *
It is rather inefficient: suppose if you have 50 datasources. Application will use be 300 connections to db.

Server log:

Code:

    criteria:{
    },
    operationConfig:{
        dataSource:"dsdb_sqlKlienci",
        operationType:"fetch",
        textMatchStyle:"substring"
    },
    startRow:0,
    endRow:75,
    componentId:"isc_ListGrid_6",
    appID:"builtinApplication",
    operation:"dsdb_sqlKlienci_fetch",
    oldValues:{
    }
}
=== 2012-05-24 13:29:08,918 [80-4] INFO  IDACall - Performing 1 operation(s)
=== 2012-05-24 13:29:08,919 [80-4] DEBUG AppBase - [builtinApplication.dsdb_sqlKlienci_fetch] No userTypes defined, allowing anyone access to all operations for this application
=== 2012-05-24 13:29:08,919 [80-4] DEBUG AppBase - [builtinApplication.dsdb_sqlKlienci_fetch] No public zero-argument method named '_dsdb_sqlKlienci_fetch' found, performing generic datasource operation
=== 2012-05-24 13:29:08,919 [80-4] INFO  SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] Performing fetch operation with
	criteria: {}	values: {}
=== 2012-05-24 13:29:08,919 [80-4] INFO  SQLWhereClause - [builtinApplication.dsdb_sqlKlienci_fetch] empty condition
=== 2012-05-24 13:29:08,919 [80-4] INFO  SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] derived query: SELECT $defaultSelectClause FROM $defaultTableClause WHERE $defaultWhereClause
=== 2012-05-24 13:29:08,920 [80-4] DEBUG SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] Executing row count query: SELECT COUNT(*) FROM $defaultTableClause WHERE $defaultWhereClause
=== 2012-05-24 13:29:08,920 [80-4] DEBUG SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] Eval'd row count query: SELECT COUNT(*) FROM Klient WHERE ('1'='1')
=== 2012-05-24 13:29:08,921 [80-4] DEBUG PoolableSQLConnectionFactory - [builtinApplication.dsdb_sqlKlienci_fetch] Returning unpooled Connection
=== 2012-05-24 13:29:08,921 [80-4] INFO  SQLDriver - [builtinApplication.dsdb_sqlKlienci_fetch] Executing SQL query on 'java:comp/env/jdbc/sql_db': SELECT COUNT(*) FROM Klient WHERE ('1'='1')
=== 2012-05-24 13:29:08,922 [80-4] DEBUG SQLServerDriver - [builtinApplication.dsdb_sqlKlienci_fetch] SQL Server version is '10.00.5500'
=== 2012-05-24 13:29:08,922 [80-4] DEBUG SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] Using SQL Limit query
=== 2012-05-24 13:29:08,922 [80-4] DEBUG SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] Using PK as default sorter: KlientID
=== 2012-05-24 13:29:08,922 [80-4] DEBUG SQLDataSource - [builtinApplication.dsdb_sqlKlienci_fetch] SQL windowed select rows 0->75, result size 75. Query: SELECT * FROM (SELECT *, ROW_NUMBER() OVER (ORDER BY x.KlientID) AS rowID FROM (SELECT TOP 100 PERCENT  Klient.AdresIKorespondencjiID, Klient.AdresSiedzibyID, Klient.AktualneZatrudnienie, Klient.BranzaID, Klient.DataRozpoczeciaDzial, Klient.EDGNr, Klient.EDGUrzad, Klient.FormaPrawnaID, Klient.FormaRozliczeniaPodID, Klient.FunduszID, Klient.KRS, Klient.KlasyfikacjaMSPID, Klient.KlientID, Klient.NIP, Klient.Nazwa, Klient.NazwaS, Klient.PKDID, Klient.PlanowaneZatrudnienie, Klient.REGON, Klient.SadRejestrowy, Klient.TypSprawozdawczosciID, Klient.Usuniety FROM Klient WHERE ('1'='1')) x) y WHERE y.rowID BETWEEN 1 AND 75
=== 2012-05-24 13:29:08,923 [80-4] DEBUG PoolableSQLConnectionFactory - [builtinApplication.dsdb_sqlKlienci_fetch] Returning unpooled Connection
=== 2012-05-24 13:29:08,928 [80-4] INFO  DSResponse - [builtinApplication.dsdb_sqlKlienci_fetch] DSResponse: List with 61 items
=== 2012-05-24 13:29:08,928 [80-4] DEBUG RPCManager - Content type for RPC transaction: text/plain; charset=UTF-8
=== 2012-05-24 13:29:08,939 [80-4] DEBUG XML - Parsed XML from (in memory stream): 1ms
=== 2012-05-24 13:29:08,940 [80-4] DEBUG RPCManager - non-DMI response, dropExtraFields: false
=== 2012-05-24 13:29:08,950 [80-4] DEBUG XML - Parsed XML from (in memory stream): 1ms

**Isomorphic** · 24 May 2012, 10:11

You should see that pooling is automatically disabled when JNDI is used, but regardless, you can set sql.pool.enabled:false to turn off.

**alibaba2** · 25 May 2012, 02:43

I finally found cause of this problem: hibernate was saturating its connection pool.
This bug (?) appeared _only when_ I was making a call to other database (smartgwt sql datasource) and call to hibernate in very close time dostance.

The solution was to add

Code:

<prop key="hibernate.connection.release_mode">after_statement</prop>

in hibernate configuration.

This works for Hibernate 3.3.

Announcement

Connections leak in SQL Datasource

Comment

Comment

Comment