You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Jerry Cwiklik (Created) (JIRA)" <de...@uima.apache.org> on 2012/01/06 22:42:42 UTC

[jira] [Created] (UIMA-2317) Fix a Deadlock in UIMA AS client

Fix a Deadlock in UIMA AS client 
---------------------------------

                 Key: UIMA-2317
                 URL: https://issues.apache.org/jira/browse/UIMA-2317
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.4.0AS


UIMA AS client code uses double synchronization on the same lock for no reason. Also, in some cases code uses more than one lock which can cause a deadlock if another thread also tries to acquire the same locks. This has only been seen/reported once. Relax use of synchronization and refactor code to prevent deadlocks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (UIMA-2317) Fix a Deadlock in UIMA AS client

Posted by "Jerry Cwiklik (Closed) (JIRA)" <de...@uima.apache.org>.

     [ https://issues.apache.org/jira/browse/UIMA-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-2317.
-------------------------------

    Resolution: Fixed

Removed unnecassary synchronization and removed code that depended on holding two different locks
                
> Fix a Deadlock in UIMA AS client 
> ---------------------------------
>
>                 Key: UIMA-2317
>                 URL: https://issues.apache.org/jira/browse/UIMA-2317
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.0AS
>
>
> UIMA AS client code uses double synchronization on the same lock for no reason. Also, in some cases code uses more than one lock which can cause a deadlock if another thread also tries to acquire the same locks. This has only been seen/reported once. Relax use of synchronization and refactor code to prevent deadlocks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira