WebSphere Commerce suite - Connection Pool Cleanup

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Commerce suite > January 2004 > Connection Pool Cleanup





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Connection Pool Cleanup
Matt Fleming

2004-01-19, 2:48 pm

Hi everyone,

Has anyone else noticed that WCS doesn't seem to clean up database
connections properly? Could you guys give me some of your experiences on
this topic? We have had to set our Connection/orphan/idle timeouts to 180
seconds in order for our site to perform at all. What are your settings?
Maybe I am just missing something..

-Matt


Glen Burson

2004-01-19, 2:48 pm

Hi Matt,

Just from experience, connection cleanup problems are almost always because
they aren't being closed by the application code. Sounds obvious, but if you
have any custom code, make sure the db connection is closed (and so returned
to the pool) in a finally block in the method that uses it.

Cheers,
Glen.

"Matt Fleming" <xagloel02@sneakemail.com> wrote in message
news:bpar2l$2d82$1@news.boulder.ibm.com...
quote:

> Hi everyone,
>
> Has anyone else noticed that WCS doesn't seem to clean up database
> connections properly? Could you guys give me some of your experiences on
> this topic? We have had to set our Connection/orphan/idle timeouts to 180
> seconds in order for our site to perform at all. What are your settings?
> Maybe I am just missing something..
>
> -Matt
>
>




Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com