-
Bug
-
Resolution: Done
-
Major
-
7.3.0.GA
-
3
-
Documentation (Ref Guide, User Guide, etc.)
-
-
-
-
-
-
+
-
Bulk 102 - Sep 22 - Oct 6, Bulk 103- Oct 7 - Oct 22, Bulk 104- Oct 23 - Nov 5
Feedback from customer:
------------------------------------------
Hello,
I would like to have a couple of questions clarified regarding JBoss EAP 7.3 chapter 8.6 Messaging Behind a Load Balancer.[1] My questions are probably self evident to any experienced JBoss administrator, but please indulge me.
We are currently running a JBoss EAP 7.2.0 cluster behind a static Undertow load balancer and have external JMS clients using JBoss client version 7.0.0 connecting to the cluster using the load balancer URL as initial context provider URL (Context.PROVIDER_URL).
This seems to work without problems, and we are now migrating to JBoss EAP and JBoss client version 7.3.
1. The documentation says "If you are doing JNDI lookups behind a load balancer, you must configure the back-end messaging workers". Does this imply that if the JMS client is running inside a JBoss EAP cluster behind a load balancer, and if it is connecting to an external JMS provider I should "configure the back-end messaging workers"?
Or does it apply to our topology, where our external JMS client is doing lookups (initialContext.lookup("jms/RemoteConnectionFactory")) using the JBoss EAP cluster load balancer URL as the initial context provider URL?
- is cloned by
-
JBEAP-20384 Messaging Behind a Load Balancer Documentation Unclear
- Closed