[
https://issues.jboss.org/browse/WFLY-8432?page=com.atlassian.jira.plugin....
]
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)