[jboss-jira] [JBoss JIRA] (JGRP-2000) Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications

Bela Ban (JIRA) issues at jboss.org
Tue Jan 5 11:08:00 EST 2016


     [ https://issues.jboss.org/browse/JGRP-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-2000:
---------------------------
    Fix Version/s: 3.6.7


I'll look at this before releasing 3.6.7, but I can't guarantee I'll fix it, as I never envisaged the way you use it.

> Output of ProtocolStack.printProtocolSpecAsXML() cannot be used as a protocol stack without manual modifications
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-2000
>                 URL: https://issues.jboss.org/browse/JGRP-2000
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.6.4
>            Reporter: Jim Thomas
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.6.7
>
>
> The output of printProtocolSpecAsXML does not contain the pbcast package prefix for NACKACK2, GMS, STATE, etc. so the load fails due to class load failure.
> Suggest either add org.jgroups.protocols.pbcast to the protocol loading search or write protocol names with full classpath when printing the spec.
> Might it also make sense to skip writing out deprecated parameters?
> Reason:  I'm generating my protocol stack programmatically because some of the parameter values are determined at run time.  In order to facilitate some experimentation with timeouts/retries/etc. I decided to temporarily use an xml file which I first generate by writing out the stack to an xml file which we can tweak the settings for subsequent runs.  Since every member has a unique protocol stack keeping the edits to a minimum is helpful.  (Maybe using property variables would be a better approach for me?)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list