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 (JIRA)" <ui...@incubator.apache.org> on 2008/10/27 16:24:44 UTC

[jira] Created: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
------------------------------------------------------------------------

                 Key: UIMA-1216
                 URL: https://issues.apache.org/jira/browse/UIMA-1216
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
            Reporter: Jerry Cwiklik


UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1216:
--------------------------------

    Attachment: uimaj-as-jms-UIMA-1216-patch-Release-2-2-2.txt

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch-Release-2-2-2.txt, uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1216:
--------------------------------

    Description: UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.  (was: UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.)

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1216:
--------------------------------

    Attachment: uimaj-as-jms-UIMA-1216-patch.txt

Fixed NPE while handling exceptions that dont contain Cas Reference Id

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1216.
-------------------------------

    Resolution: Fixed

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch-Release-2-2-2.txt, uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1216:
--------------------------------

    Fix Version/s: 2.3AS

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3AS
>
>         Attachments: uimaj-as-jms-UIMA-1216-patch-Release-2-2-2.txt, uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1216.
-------------------------------

    Resolution: Fixed

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1216:
--------------------------------

    Attachment:     (was: uimaj-as-jms-UIMA-1216-patch.txt)

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1216:
--------------------------------

    Attachment: uimaj-as-jms-UIMA-1216-patch.txt

Modified UIMA-AS client code to release CASes while handling a process exception. The code releases a CAS and removes CAS entry from the cache after calling user code( listener).

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Reopened: (UIMA-1216) UIMA AS Client Code Doesn't Release CAS While Handling Process Exception

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik reopened UIMA-1216:
---------------------------------

      Assignee: Jerry Cwiklik

Reopened to attach a patch for 2.2.2 release

> UIMA AS Client Code Doesn't Release CAS While Handling Process Exception
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1216
>                 URL: https://issues.apache.org/jira/browse/UIMA-1216
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>         Attachments: uimaj-as-jms-UIMA-1216-patch.txt
>
>
> UIMA AS client framework code caches a CAS before sending (async) request to UIMA AS service. When the reply is received the CAS is retrieved from the cache, the client (user) code is called via a listener and the CAS is subsequently released.  For synchronous calls the user code is responsible for each CAS release. When a reply containing an exception is received (for both sync and async send), the exception handler notifies the user code but never releases the CAS. This may lead to hangs and may impact performance since some CASes are never released.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.