[
https://jira.duraspace.org/browse/DS-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-1458:
----------------------------
Status: Accepted (was: Received)
> Connection pool exhausted
> -------------------------
>
> Key: DS-1458
> URL: https://jira.duraspace.org/browse/DS-1458
> Project: DSpace
> Issue Type: Bug
> Components: DSpace API
> Affects Versions: 1.7.2, 1.8.0, 1.8.1, 3.0
> Reporter: Bram Luyten (@mire)
> Assignee: Bram Luyten (@mire)
> Attachments: postgres_connections_ALL-year.png,
> postgres_connections_db-year.png
>
>
> This issue follows from a recent discussion on the mailing list:
> http://comments.gmane.org/gmane.comp.db.dspace.user/18148
> Peter Dietz reported that changing the behaviour of the connection pool,
> allowing automatic growth, fixed the errors for him:
> https://github.com/osulibraries/DSpaceOSUKB/commit/c627ebdb738efbf46ba7a338180099fa38b96a66.diff
> This still doesn't quite uncover if the connection pool is being managed full
> proof (e.g. are connections always properly returned or not?)
> Also, the default value of 30 for max connections in the default DSpace 3.0
> build properties might be too low to start with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
