[
https://issues.jboss.org/browse/WFLY-8432?page=com.atlassian.jira.plugin....
]
Heribert Steuer edited comment on WFLY-8432 at 5/22/17 3:34 PM:
----------------------------------------------------------------
Hello Bartosz,
thanks alot for this patch, it pretty much solves the issue with the missing outbound
mapping. I have successfully ran JMS through an Apache reverse proxy. Unfortunately it did
not work when the proxy did SSL offloading, but thats another story. Thanks alot for your
work, Cheers!
was (Author: patronas):
Hello Bartosz,
thanks alot for this patch. I have applied your changed to the 10.x branch and did some
tests to run the jmx quickstart project through the proxy. Running the test without the
reverse proxy works well, after adding
the appropriate client-mapping attribute to the socket-binding and looping traffic through
the proxy leads to exceptions at the client level (see below).
Is there probably anything missing in order to run JMS through a reverse proxy?
After a successful looking up the queue using JNDI, the client throws the following
exception:
bq. Exception in thread "main" javax.jms.JMSRuntimeException: Failed to create
session factory
bq. at
org.apache.activemq.artemis.jms.client.JmsExceptionUtils.convertToRuntimeException(JmsExceptionUtils.java:88)
bq. at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:262)
bq. at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:248)
bq. at
org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.makeJmsCall(RemoteEJBClient.java:320)
bq. at
org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:56)
bq. Caused by: javax.jms.JMSException: Failed to create session factory
bq. at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:727)
bq. at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createContext(ActiveMQConnectionFactory.java:255)
bq. ... 3 more
bq. Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007:
Cannot connect to server(s). Tried with all available servers.]
bq. at
org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:778)
bq. at
org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory.createConnectionInternal(ActiveMQConnectionFactory.java:724)
bq. ... 4 more
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
Fix For: 11.0.0.Beta1
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)