Bug 1268186 - [GSS](6.4.z) ManagedSocketFactory doesn't work for client sockets
Summary: [GSS](6.4.z) ManagedSocketFactory doesn't work for client sockets
Keywords:
Status: CLOSED DUPLICATE of bug 1268185
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering
Version: 6.4.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Enrique Gonzalez Martinez
QA Contact: Jitka Kozana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-02 03:38 UTC by dereed
Modified: 2019-08-15 05:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-23 02:35:31 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-1029 0 Major Resolved ManagedSocketFactory doesn't work for client sockets 2016-05-23 07:46:24 UTC

Description dereed 2015-10-02 03:38:45 UTC 
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.
Comment 1 dereed 2015-10-02 03:41:31 UTC 
Fixing this is dependent on how BZ 1268185 is fixed.

(If the custom socket factory is removed, this won't be necessary in 6.4.z.  If BZ 1268185 fixes the socket factory so it's set correctly, this is required).
Comment 2 dereed 2015-10-23 02:35:31 UTC 
The PR for BZ 1268185 makes this no longer an issue.
(the calls from ManagedSocketFactory to SocketBindingManagerImpl that trigger the issue were removed).
Comment 3 Enrique Gonzalez Martinez 2015-10-23 06:40:31 UTC 
This bug is fixed with BZ 1268185 so this should be closed as duplicate.

*** This bug has been marked as a duplicate of bug 1268185 ***
Note You need to log in before you can comment on or make changes to this bug.