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/04/25 16:47:56 UTC
[jira] Created: (UIMA-1018) Disable Timers on Connections to Reply
Queues
Disable Timers on Connections to Reply Queues
---------------------------------------------
Key: UIMA-1018
URL: https://issues.apache.org/jira/browse/UIMA-1018
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Fix For: 2.2.2AS
Modify the OutputChannel code of the UIMA-AS service to disable Timers on connections to Reply Queues. Currently, the code starts a timer every time a reply is sent to a reply queue. This causes problems in deployments that use long running analytics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1018) Disable Timers on Connections to Reply
Queues
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1018:
--------------------------------
Attachment: uimaj-as-activemq-UIMA-1018-patch.txt
Disables timers on connections to reply queues. Connections to reply queues no longer expire.
> Disable Timers on Connections to Reply Queues
> ---------------------------------------------
>
> Key: UIMA-1018
> URL: https://issues.apache.org/jira/browse/UIMA-1018
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.2.2AS
>
> Attachments: uimaj-as-activemq-UIMA-1018-patch.txt
>
>
> Modify the OutputChannel code of the UIMA-AS service to disable Timers on connections to Reply Queues. Currently, the code starts a timer every time a reply is sent to a reply queue. This causes problems in deployments that use long running analytics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1018) Disable Timers on Connections to Reply
Queues
Posted by "Burn Lewis (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Burn Lewis updated UIMA-1018:
-----------------------------
Attachment: UIMA-1018-B.patch
Also disable timers on requests to co-located delegates.
Make a few log messages print meaningful names instead of class hashcodes.
> Disable Timers on Connections to Reply Queues
> ---------------------------------------------
>
> Key: UIMA-1018
> URL: https://issues.apache.org/jira/browse/UIMA-1018
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.2.2AS
>
> Attachments: UIMA-1018-B.patch, uimaj-as-activemq-UIMA-1018-patch.txt
>
>
> Modify the OutputChannel code of the UIMA-AS service to disable Timers on connections to Reply Queues. Currently, the code starts a timer every time a reply is sent to a reply queue. This causes problems in deployments that use long running analytics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1018) Disable Timers on Connections to Reply
Queues
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein closed UIMA-1018.
-------------------------------
Resolution: Fixed
> Disable Timers on Connections to Reply Queues
> ---------------------------------------------
>
> Key: UIMA-1018
> URL: https://issues.apache.org/jira/browse/UIMA-1018
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Fix For: 2.2.2AS
>
> Attachments: UIMA-1018-B.patch, uimaj-as-activemq-UIMA-1018-patch.txt
>
>
> Modify the OutputChannel code of the UIMA-AS service to disable Timers on connections to Reply Queues. Currently, the code starts a timer every time a reply is sent to a reply queue. This causes problems in deployments that use long running analytics.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.