[ 
http://mifosforge.jira.com/browse/MIFOS-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Vorburger updated MIFOS-5096:
-------------------------------------

    Summary: Configure c3p0 pool to never wait indefinitely for connections 
(checkoutTimeout=1000)  (was: Configure c3p0 pool to never wait indefinitely 
for connections, and debug unreturned connections to identify leaks)

On second thought, Udai you are absolutely right of course - enabling a 
configuration by default which just lets c3p0 kill off connections after a 
certain amount of time is certainly not a good idea - this wasn't one of my 
brighter late night thoughts. :)

Re. providing a way so that users can set this, it's indeed not currently 
possible via local.properties (I've briefly tested this), but with a 
c3p0.properties in WEB-INF/classes (with the unreturnedConnectionTimeout 
commented out) people who want to try this e.g. in dev could simply uncomment 
that there (and be careful not to commit it - like with any other temp. dev 
change) - that's "good enough" for now?

> Configure c3p0 pool to never wait indefinitely for connections 
> (checkoutTimeout=1000)
> -------------------------------------------------------------------------------------
>
>                 Key: MIFOS-5096
>                 URL: http://mifosforge.jira.com/browse/MIFOS-5096
>             Project: mifos
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Critical
>         Attachments: c3p0.properties
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I've spent a few hours today digging into Connection Pooling to try to help 
> with MIFOSSUPPORT-92.
> As part of that I've read http://www.mchange.com/projects/c3p0/, and would 
> like to propose that we include the attached c3p0.properties.
> This configuration causes the c3p0 connection pool a) to never wait 
> indefinitely for connections, and b) forcibly terminate connections that were 
> likely - and tell us where they leaked from!
> We could also set that unreturnedConnectionTimeout to something higher than 
> 30, if anybody thinks we should be more prudent.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that
has been used successfully in hundreds of IBM storage optimization engage-
ments, worldwide.  Store less, Store more with what you own, Move data to 
the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to