Connection Problems 1

[javoine]

Greets,

I don't know if this should be in this(Tomcat) section or the JSP area, but here goes...

I have a simple web application using 2 java classes to access connection information.

I call the classes from a JSP page and establish my connection.

Then, I close my connections and any statements/recordsets, etc...

BUT: when only 1 page is testing it, it appears to work fine and eventually connections close, but when multiple user have used the app, the connections wont die?

how do kill all my connections when no one else is using the app?

thanx in advance for any info you might have

 

[sedj]

Are you using a connection pool ?
Are you attempting to use concurrent data requests on the same Connection ?

 

[javoine]

sedj,

faithful hero, glad to see you here. yes, although i do not have control over this database (postgres), I was told that we are using a connection pool.

In other products that I have used, the connection pool will kill the connection after some said timeout period,

in this case though, when multiple users have the page, it creates new simultaneous connections and they seem to remain open to the point where tomcat needs to be restarted in order to free the connections to the database.

any suggestions are welcome...thanx
...

 

[sedj]

And you definitely close the ResultSet, Statement/CallableStaement and Connection objects ?

If so, try to monitor the state of the connections db side, and add debug code to make sure you are definitely closing all db-related objects and connections.

What drivers are you using ?

 

[javoine]

i am absolutely positive that i close all my objects. i dont really have that many, but i do close each one.

the driver i am using is: jdbcostgresql

jdbc uses connection pooling, but does not kill the connections after a time limit, so they remain open to the server database, i am taking your suggestion and trying to monitor and debug, if you have any other suggestions, please feel free...and thank you again as always!