[
https://issues.jboss.org/browse/AS7-5107?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on AS7-5107:
----------------------------------------------
Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug
1001612|https://bugzilla.redhat.com/show_bug.cgi?id=1001612]
BZ was verified in EAP 6.2.0.ER4 by following batch:
batch
/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector)
/subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name,value=dg-group1)
run-batch
In this way connector for connection factory can be undefined and set discovery-group. Or
discovery-group undefined and changed set connector.
This must be done in a batch or commands will fail as it is reported in description.
define connectors as alternatives to discovery-group
----------------------------------------------------
Key: AS7-5107
URL:
https://issues.jboss.org/browse/AS7-5107
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
Fix For: EAP 6.1.0.Alpha (7.2.0.Final)
cluster-connections, bridges and JMS connection factories must define either connectors
or discovery-group but not both.
The choice is handled in the messaging susbsystem parser but it's not enforced by the
attributes' definitions. Admin operations are not shielded against a misconfiguration
by changing directly these attributes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira