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

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

GitHub user michaelandrepearce opened a pull request:

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

    ARTEMIS-857 Add JMX endpoints to view and reset groups

    Expose method to return current mappings of groups to consumers
    Expose methods to reset (remove) specific group mapping from groupID to 
Consumer
    Expose methods to reset (remove) all group mappings

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

    $ git pull https://github.com/michaelandrepearce/activemq-artemis 
ARTEMIS-857

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

    https://github.com/apache/activemq-artemis/pull/2023.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 #2023
    
----
commit c28a27d5db942d2a148adaff2e0b90f4863233f1
Author: Michael André Pearce <michael.andre.pearce@...>
Date:   2018-04-16T16:11:44Z

    ARTEMIS-857 Add JMX endpoints to view and reset groups
    
    Expose method to return current mappings of groups to consumers
    Expose methods to reset (remove) specific group mapping from groupID to 
Consumer
    Expose methods to reset (remove) all group mappings

----


> JMX+API support for viewing and manually clearing message group caches
> ----------------------------------------------------------------------
>
>                 Key: ARTEMIS-857
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-857
>             Project: ActiveMQ Artemis
>          Issue Type: Sub-task
>          Components: Broker
>            Reporter: Matt Pavlovich
>            Priority: Major
>
> Need an API to support for viewing message group infomration and optionally 
> flushing group-id maps that are not cleared by mis-behaving clients.
> ie.. client never sends the JMSXSeqID -1 message



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

Reply via email to