DB connection leak in DAVServlet
--------------------------------
Key: DS-1074
URL: https://jira.duraspace.org/browse/DS-1074
Project: DSpace
Issue Type: Bug
Components: LNI
Affects Versions: 1.8.0, 1.7.2, 1.6.2, 1.5.2
Reporter: Bo Gundersen
Priority: Major
Attachments: dspace-1.5.2_connection_fix.diff,
dspace-1.6.2_connection_fix.diff, dspace-1.7.2_connection_fix.diff,
dspace-1.8.0_connection_fix.diff
When using basic authentication, the DAVServlet leaks a connection each time a
session is authenticated.
The authenticate method constructs a Context (which in turn allocates a DB
connection), but the Context is not closed or returned from the method in the
case where a "WWW-Authenticate" header is sent back.
Also, if an error occurs in the processing of the authentication, the context
is also not closed.
I have attached patches for versions 1.5.2, 1.6.2, 1.7.2 and 1.8.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
