[jboss-jira] [JBoss JIRA] (WFLY-5449) Custom socket factory for JGroups subsystem not set correctly

[Dennis Reed (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125504#comment-13125504 ] 

Dennis Reed commented on WFLY-5449:
-----------------------------------

The issue with FD_SOCK's socket factory still not being set in EAP 6 after backporting this is a bug in JGroups, and does not affect Wildfly.
Re-closing this issue.

> Custom socket factory for JGroups subsystem not set correctly
> -------------------------------------------------------------
>
>                 Key: WFLY-5449
>                 URL: https://issues.jboss.org/browse/WFLY-5449
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.CR2
>            Reporter: Dennis Reed
>            Assignee: Paul Ferraro
>            Priority: Blocker
>             Fix For: 10.0.0.CR4
>
>
> Wildfly's JChannelFactory tries to set a custom socket factory on the JGroups transport.
> This is not the correct API to use, and it gets overwritten when the JGroups channel starts.
> A custom socket factory should be set on the JChannel.
> The only time the custom socket factory is currently used is if there's a race condition where two channels are started at the same time, and the custom factory is set just before the other channel uses it.



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