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