Skip to content

Changing the way to interact with JGroups in the ResourceAdapter#221

Open
ehsavoie wants to merge 1 commit intorh-messaging:jboss-1.5.5-xfrom
ehsavoie:jboss-jgroup-channel
Open

Changing the way to interact with JGroups in the ResourceAdapter#221
ehsavoie wants to merge 1 commit intorh-messaging:jboss-1.5.5-xfrom
ehsavoie:jboss-jgroup-channel

Conversation

@ehsavoie
Copy link

Obtaining a BroadCastEndpointFactory instead of a JChannel to connect to JGroups to avoid issue and leak with JChannel lifecyle.

@JBossJenkins
Copy link

Can one of the admins verify this patch?

Obtaining a BroadCastEndpointFactory instead of a JChannel to connect to JGroups to avoid issue and leak with JChannel lifecyle.
Object o = aClass.newInstance();
Method m = aClass.getMethod("locateChannel", new Class[]{String.class});
return (JChannel) m.invoke(o, name);
Method m = aClass.getMethod("locateBroadcastEndpointFactory", new Class[]{String.class});
Copy link

@pferraro pferraro Aug 24, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I worry about how this change affects compatibility. Existing usage of the jgroupsChannelLocatorClass property will break, as the value provided will not have this method.
This change isn't strictly required to fix https://issues.jboss.org/browse/WFLY-9246, so long as the messaging-activemq subsystem is able to override the broadcast endpoint logic used by the resource adapter logic, which 1692f78 already allows.

@JBossJenkins
Copy link

Can one of the admins verify this patch?

1 similar comment
@JBossJenkins
Copy link

Can one of the admins verify this patch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants