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

[Speelmon, Lance Day]

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  
batch should be running out of a separate pool to allow this kind of  
troubleshooting?  L


Lance Speelmon
Scholarly Technologist

On Sep 17, 2009, at 2:31 PM, Seth Theriault wrote:

> Sean DeMonner wrote:
>
>> We've wondered that too, but haven't found anything that is
>> running at those times. The jumps are also not consistently
>> spaced so we haven't seen a pattern.
>
> I am thinking that there is some new JDBC-related code in 2.6 and
> the database connections are not being closed properly (I guess
> in this case, it would mean releasing the conns back to the
> pool). I know that Michigan has the capacity to have a large sets
> of results returned from any query.
>
> Just a thought.
>
> Seth
>
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
>
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org 
>  with a subject of "unsubscribe"