You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <ui...@incubator.apache.org> on 2008/10/29 19:52:46 UTC
[jira] Created: (UIMA-1220) CASes are not released from remote CAS
Multipliers when the reply queue is remote
CASes are not released from remote CAS Multipliers when the reply queue is remote
---------------------------------------------------------------------------------
Key: UIMA-1220
URL: https://issues.apache.org/jira/browse/UIMA-1220
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.2.2
Reporter: Burn Lewis
Priority: Minor
The ReleaseCas request is sent to the wrong queue so the CAS pool is soon exhausted and the CM hangs. If the reply queue is local (tcp connected) all is well.
This has been fixed in the latest code which uses temporary queues (and so will be incompatible with the 2.2.2 build)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1220) CASes are not released from remote CAS
Multipliers when the reply queue is remote
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1220.
--------------------------------
Resolution: Won't Fix
Fix Version/s: 2.3AS
This is fixed in 2.3.
For 2.2.2, the work-around for this is to use local reply queues with remote CAS multipliers.
This isn't possible if using HTTP as the messaging protocol - in that case, please apply this patch to your 2.2.2 release.
> CASes are not released from remote CAS Multipliers when the reply queue is remote
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1220
> URL: https://issues.apache.org/jira/browse/UIMA-1220
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Burn Lewis
> Priority: Minor
> Fix For: 2.3AS
>
> Attachments: UIMA-1220.patch
>
>
> The ReleaseCas request is sent to the wrong queue so the CAS pool is soon exhausted and the CM hangs. If the reply queue is local (tcp connected) all is well.
> This has been fixed in the latest code which uses temporary queues (and so will be incompatible with the 2.2.2 build)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1220) CASes are not released from remote CAS
Multipliers when the reply queue is remote
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burn Lewis updated UIMA-1220:
-----------------------------
Attachment: UIMA-1220.patch
Here's a patch that fixes the problem by ensuring the the queue name is not changed if it ends in __CasSync
> CASes are not released from remote CAS Multipliers when the reply queue is remote
> ---------------------------------------------------------------------------------
>
> Key: UIMA-1220
> URL: https://issues.apache.org/jira/browse/UIMA-1220
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Affects Versions: 2.2.2
> Reporter: Burn Lewis
> Priority: Minor
> Attachments: UIMA-1220.patch
>
>
> The ReleaseCas request is sent to the wrong queue so the CAS pool is soon exhausted and the CM hangs. If the reply queue is local (tcp connected) all is well.
> This has been fixed in the latest code which uses temporary queues (and so will be incompatible with the 2.2.2 build)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.