[
https://issues.apache.org/jira/browse/DIRSERVER-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRSERVER-1782.
------------------------------------------
Resolution: Fixed
Fixed with http://svn.apache.org/viewvc?rev=1422718&view=rev
> The various locks we are using may not be released in some case
> ---------------------------------------------------------------
>
> Key: DIRSERVER-1782
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1782
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M8
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-M9
>
>
> There are many places in the server where we are using a lock, and release
> without any consideration to the potential exception that could occurs after
> we have acquired the lock but before we have released it.
> The standard form should be :
> lock.acquire();
> try
> {
> // do something
> }
> finally
> {
> lock.release();
> }
> Note that the lock acquisition is done *outside* of the try{} just to protect
> us from a potential excpetion that would lead to another exception being
> generated when we will ry to do a lock.release()
--
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
