[jboss-jira] [JBoss JIRA] Updated: (JBAS-5090) Use Channel.setInfo() to provide data to JGroups probe
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Tue Jan 20 15:05:06 EST 2009
[ https://jira.jboss.org/jira/browse/JBAS-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated JBAS-5090:
-----------------------------------
Fix Version/s: Backlog
> Use Channel.setInfo() to provide data to JGroups probe
> ------------------------------------------------------
>
> Key: JBAS-5090
> URL: https://jira.jboss.org/jira/browse/JBAS-5090
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Clustering
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Optional
> Fix For: Backlog
>
>
> Think about ways to take advantage of following from Bela Ban:
> Okay, I've added an "info" paremeter to Probe, so you can run
> JGroups/bin/probe.sh -timeout 1000 -query info
> and this will dump *any* information that was added via Channel.setInfo(String key,Object val). The val will be written to a StringBuilder, so make sure you place only values into info which have a meaningful toString().
> This can be used to dump buddy replication information.
> However, any application which has access to a channel can add information which is useful on a probe, e.g.
> * JBossCache
> o Version
> o Buddy replication info
> o Number of nodes, attrs
> o Config info
> * Clustering
> o Different clusters a node is part of
> o Node name
> o Config info
> The Probe utility is quick and dirty and - since it uses IP multicasts - cannot dump more than 65K worth of data, so make sure you don't cram everything in there ...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list