[ 
https://issues.apache.org/jira/browse/ARTEMIS-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383779#comment-16383779
 ] 

ASF GitHub Bot commented on ARTEMIS-1696:
-----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1924

    ARTEMIS-1696 doc updates

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1696

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1924.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1924
    
----
commit 3d4b52df9dfd1ac95ffd59dd06c813fa770f8989
Author: Justin Bertram <jbertram@...>
Date:   2018-02-22T16:15:52Z

    ARTEMIS-1696 doc updates

----


> Allow empty 'address' for grouping-handler
> ------------------------------------------
>
>                 Key: ARTEMIS-1696
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1696
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.5.0
>
>
> The {{address}} of {{grouping-handler}} should match the {{address}} of the 
> associated {{cluster-connection}}.  However, the {{address}} of 
> {{cluster-connection}} can be undefined (i.e. null or empty string) but the 
> {{address}} of {{grouping-handler}} cannot.  The most common use-case for 
> {{cluster-connection}} is to have an empty or undefined {{address}} (so that 
> all addresses will be clustered).  The {{address}} of {{grouping-handler}} 
> should support this as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to