[
https://issues.jboss.org/browse/JGRP-2331?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2331:
--------------------------------
Duplicate protocols are now listed, dupes have their {{id}} as suffix:
{noformat}
[belasmac] /Users/bela/JGroups$ probe.sh jmx=FRAG2.frag_
#1 (155 bytes):
local_addr=X [ip=192.168.1.105:7800, version=4.1.3-SNAPSHOT (Mont Ventoux), cluster=draw,
1 mbr(s)]
FRAG2={frag_size=60000}
FRAG2-1230={frag_size=20000}
1 responses (1 matches, 0 non matches)
{noformat}
Probe does not handle multiple protocols of the same class in the
same stack
----------------------------------------------------------------------------
Key: JGRP-2331
URL:
https://issues.jboss.org/browse/JGRP-2331
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Optional
Fix For: 4.1.3
When we have multiple protocols of the same type (e.g. FRAG2) in the same stack, probe.sh
only dumps information about the first one found. E.g. in
{noformat}
<UDP/>
<PING/>
<FRAG2 id="350".../>
...
<GMS/>
<FRAG2.../>
{noformat}
, the FRAG2 protocol with id 350 would likely get skipped as the other one was found
first in a query like {{probe.sh jmx=FRAG2}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)