Jdbc connection leak problem in wls 8.1 sp1

Question

Fellows!
I have problem finding a jdbc connection leak and hope to get some tips from
a som friendly person who has some experience about this.
The application contains some 100 classes and CMP beans.
All connections are fetched with datasource.getConnection and are realesed
in finally() immediately after the sql-query is done.
Except for the entity beans of course which has the transaction required
attribute set.
Any ideas much appreciated!
Best regards from the top of Europe - Luleå.
Here the first snow has been falling and thin ice has freezed on the gulf of
bothnia.
Stefan

Answer 1

Stefan Johansson wrote:
Fellows!
I have problem finding a jdbc connection leak and hope to get some tips from
a som friendly person who has some experience about this.
The application contains some 100 classes and CMP beans.
All connections are fetched with datasource.getConnection and are realesed
in finally() immediately after the sql-query is done.
Except for the entity beans of course which has the transaction required
attribute set.Hi. I don't understand this last 'except'. All jdbc code in bean methods
should be defining a connection as a method variable, obtaining it from
a TxDataSource in a try block, used completely, and closed as the only/first
thing in the finally block. We will handle the close() correctly, it won't
hurt the tx if there is one, and it will do the right thing if there isn't one.
How do you know there's a leak? Usually our leak-detection shows where the connection
was made, so you can find out why it wasn't closed...
Joe
>
Any ideas much appreciated!
Best regards from the top of Europe - Luleå.
Here the first snow has been falling and thin ice has freezed on the gulf of
bothnia.
Stefan