[Deploying Sakai] [Building Sakai] Strange database connection memory issue at U-M

R.P. Aditya rpaditya at umich.edu
Tue Sep 22 10:53:59 PDT 2009

On 2009-09-17, Speelmon, Lance Day <lance at indiana.edu> wrote:
> Perhaps - probably the right place to start looking.  The problem is  
> that the tools to help troubleshoot these kind of leaks cannot be used  
> in production environments.  For example, if you tell the connection  
> pool to force return connections to the pool after a set amount of  
> time - it interferes with batch activities.  So, then the question  
> becomes: can these leaks be triggered in a test environment?  Or maybe  

we are unable to trigger the memory usage jump in a test environment so far

> batch should be running out of a separate pool to allow this kind of  
> troubleshooting?  L

yes, batch processes should use a separate pool (or even a one-time
connection rather than a pool if that's easier), definitely


More information about the production mailing list