[jboss-jira] [JBoss JIRA] (AS7-6223) org.jboss.as.protocol.ProtocolChannelClient needs to support client socket bind address config
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Wed Mar 6 11:21:56 EST 2013
[ https://issues.jboss.org/browse/AS7-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
RH Bugzilla Integration updated AS7-6223:
-----------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=918632, https://bugzilla.redhat.com/show_bug.cgi?id=918643 (was: https://bugzilla.redhat.com/show_bug.cgi?id=918632)
> org.jboss.as.protocol.ProtocolChannelClient needs to support client socket bind address config
> ----------------------------------------------------------------------------------------------
>
> Key: AS7-6223
> URL: https://issues.jboss.org/browse/AS7-6223
> Project: Application Server 7
> Issue Type: Feature Request
> Components: CLI, Domain Management
> Affects Versions: 7.1.0.Final
> Reporter: William DeCoste
> Assignee: William DeCoste
> Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
>
>
> OpenShift requires that the client socket bind address be set to the OPENSHIFT_INTENRAL_IP loopback. ProtocolChannelClient currently does not support config for the bind address. connect(..) should be calling
> return endpoint.connect("remote", bindAddress, destAddress, builder.getMap(), actualHandler, sslContext);
> instead of
>
> return endpoint.connect(uri, builder.getMap(), actualHandler, sslContext);
> and expose bindAddress config
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list