[jboss-jira] [JBoss JIRA] (WFLY-6594) Incorrect description of group-handler/group-timeout attribute in CLI
Chen Maoqian (JIRA)
issues at jboss.org
Thu May 5 21:55:00 EDT 2016
[ https://issues.jboss.org/browse/WFLY-6594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Maoqian moved JBEAP-4549 to WFLY-6594:
-------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6594 (was: JBEAP-4549)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMS
(was: JMS)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 10.0.0.Final
(was: 7.0.0.CR2)
> Incorrect description of group-handler/group-timeout attribute in CLI
> ---------------------------------------------------------------------
>
> Key: WFLY-6594
> URL: https://issues.jboss.org/browse/WFLY-6594
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Chen Maoqian
> Assignee: Chen Maoqian
>
> The description of group-timeout attribute in CLI says:
> bq. How long a group binding will be used, -1 means for ever. Bindings are removed after this wait elapses (only valid for LOCAL handlers).
> However the attribute is valid for both LOCAL and REMOTE handler. If you configure the attribute with REMOTE handler it specifies how often the REMOTE will notify the LOCAL that the route (group binding) was used.
> The Artemis documentation \[1\] also suggests to configure the group-timeout for REMOTE handlers.
> bq. In case you are using group-timeouts, the remote node should have a smaller group-timeout with at least half of the value on the main coordinator. This is because this will determine how often the last-time-use value should be updated with a round trip for a request to the group between the nodes.
> \[1\] https://activemq.apache.org/artemis/docs/1.1.0/message-grouping.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list