[jboss-jira] [JBoss JIRA] (WFLY-8416) Create BroadcastEndpoint implementation using WF clustering API
Paul Ferraro (JIRA)
issues at jboss.org
Tue Mar 21 18:11:00 EDT 2017
[ https://issues.jboss.org/browse/WFLY-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ferraro updated WFLY-8416:
-------------------------------
Description: The upgrade to JGroups 4.0 will break the JGroups BroadcastEndpoint implementation in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage. (was: The upgrade to JGroups 4.0 will break the JGroups usage in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage.)
> Create BroadcastEndpoint implementation using WF clustering API
> ---------------------------------------------------------------
>
> Key: WFLY-8416
> URL: https://issues.jboss.org/browse/WFLY-8416
> Project: WildFly
> Issue Type: Task
> Components: Clustering, JMS
> Affects Versions: 10.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 12.0.0.Alpha1
>
>
> The upgrade to JGroups 4.0 will break the JGroups BroadcastEndpoint implementation in ActiveMQ Artemis (which uses JGroups 3.x). JGroups is only used to broadcast/receive a byte[] to the cluster. This can be easily implemented using the WildFly clustering API. Such an implementation will simplify the transition to JGroups 4.0 and future-proof WildFly from any new API breakage.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list