[jboss-jira] [JBoss JIRA] (WFCORE-1029) ManagedSocketFactory doesn't work for client sockets

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on WFCORE-1029:
------------------------------------------

I'll keep this open because at a minimum UnnamedBindingRegistry should have javadoc declaring that the sockets and channels passed into the various register methods must be bound. Using something other than InetSocketAddress as the map key may be fine too. The basic goal here is to record all the sockets the server is opening so we can provide a comprehensive management view, so forcing people to bind before registering just gets in the way of them using the registry and may cause them to skip it. The main criteria should be "only register something you intend to bind."

> ManagedSocketFactory doesn't work for client sockets
> ----------------------------------------------------
>
>                 Key: WFCORE-1029
>                 URL: https://issues.jboss.org/browse/WFCORE-1029
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 2.0.0.CR5
>            Reporter: Dennis Reed
>            Assignee: Brian Stansberry
>
> SocketBindingManagerImpl does not work with client sockets.
> It adds sockets to a map based on local address.  Client sockets that have not been bound yet do not have a local address.
> This breaks the JGroups subsystem's ManagedSocketFactory, which uses SocketBindingManagerImpl for both server and client sockets.



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