[
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.
