[jboss-jira] [JBoss JIRA] (WFLY-8432) Support socket-binding attribute "client-mapping" in messaging subsystem
Bartosz Spyrko-Śmietanko (JIRA)
issues at jboss.org
Fri May 19 11:19:00 EDT 2017
[ https://issues.jboss.org/browse/WFLY-8432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409143#comment-13409143 ]
Bartosz Spyrko-Śmietanko commented on WFLY-8432:
------------------------------------------------
Since ActiveMQ client currently isn't capable of picking a connection based on client's network, https://github.com/wildfly/wildfly/pull/10082 uses the first mapping available for the socket binding. source-network attribute and any further client mappings are ignored.
> Support socket-binding attribute "client-mapping" in messaging subsystem
> ------------------------------------------------------------------------
>
> Key: WFLY-8432
> URL: https://issues.jboss.org/browse/WFLY-8432
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.1.0.Final
> Reporter: Jörg Bäsner
> Assignee: Bartosz Spyrko-Śmietanko
>
> The messaging subsystem doesn't take into account the "client-mapping" attribute of the <socket-binding> when creating a <http-connector>.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list