The error is not in the xml file but the source code.
Had the error a couple of times; solved it by using a
Connection conn = null;
Statement stmt = null;
ResultSet rs = null;
try {
conn = ...
stmt = conn.CreateStatement(); <- don't remember if this is correct.
rs = stmt.execute(); <- something like this.
} catch (SQLException sqle) {
}
finally {
rs.close();
stmt.close();
conn.close(); <- in that order...!
}
The idea is to close everything in the finally block and not in the try
block.
----- Original Message -----
From: "Michael Maram" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, November 22, 2000 9:26 AM
Subject: DriverManagerConnectionPoolConnection not closed, check your code!
> Hi all
>
> I am receiving the following message a number of times following multiple
> user concurrent hits -
>
> DriverManagerConnectionPoolConnection not closed, check your code!
>
> I am physically closing the connection after the process of each request.
> What does the close() method on the connection do? Will it free the
> connection back to the pool? That's what it should do. Why am I still
> getting this message? Below is my data-source definition.
>
> <data-source
> name="test1"
> class="com.evermind.sql.DriverManagerDataSource"
> ejb-location="jdbc/OracleDS1"
> pooled-location="jdbc/OraclePooledDS1"
> xa-location="jdbc/xa/OracleXADS1"
> url="jdbc:oracle:thin:@test:1521:pilot"
> connection-driver="oracle.jdbc.driver.OracleDriver"
> username="test"
> password="test"
> max-connections="500"
> />
>
> PS - I have checked the listings but found no solution.
>
> In anticipation.
>
>
