I started testing the connection pool with our application. I have an issue with the abandon connection detection. Looking at the source code the timestamp which is used to check for abandonment is updated when the connection is created, borrowed, or returned.
In our application we create a temporary table for raw data... This table is only available while using the current connection. Data in this table is processed and then saved permanently in the database. After creating/populating the temporary table the connection is kept until the data is processed, during processing queries are performed on the temporary table with this connection. The connection is being treated as abandoned after the timeout (based on the time of the borrow). Please note that this does not occur when using DBCP. It would be great to be able to have the abandoned timestamp reset when a statement is executed on the connection. If this is not possible, could it be possible to get the same connection to reset the timestamp. Any suggestions.... thanks --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org