You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2013/10/10 09:51:43 UTC

[jira] [Commented] (AMQ-4766) Expose Message Group maps via JMX

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

james strachan commented on AMQ-4766:
-------------------------------------

Agreed! If we could query the current map of hash buckets -> container IDs we could then visualise the Message Groups in hawtio ;). e.g. to see how the load balancing is working across consumers & then be able to manually rebalance if things are a bit wacky.

It might be nice if folks could enter a possible JMSXGroupID and it'd return which consumer would get it? If its not too hard; an API like this maybe (I've used Integer for the message group / hash bucket key - not sure thats the best value to use)...

{code}
/** returns the message group hashbucket/id -> consumer id */
Map<Integer, String> getMessageGroups();

/** Has the effect of sending MsgSeqId = -1 to a given message group so its rebalanced to another consumer */
void closeSequenceById(Integer id);

/** for a given JMSXGroupID find the hash bucket its in (then using getMessageGroups() you can find the consumer */
Integer getMessageGroupId(String jmsxGroupId);
{code}


> Expose Message Group maps via JMX
> ---------------------------------
>
>                 Key: AMQ-4766
>                 URL: https://issues.apache.org/jira/browse/AMQ-4766
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>    Affects Versions: 5.8.0
>         Environment: All
>            Reporter: Matt Pavlovich
>            Assignee: Rob Davies
>
> It would be really handy to have the Message Group maps exposed via JMX and to allow admins to purge, and delete unused ones w/o having to rely on the MsgSeqId="-1" message to come through.



--
This message was sent by Atlassian JIRA
(v6.1#6144)