+++ This bug was initially created as a clone of Bug #1128851 +++
Description of problem:
Currently the External Load Balancer Architecture is plug-able and allows you to choose a load balancer of your choice.
However Red Hat makes not recommendation / does not provide examples with any of its existing load balancing solutions.
An example using NGINX should be provided to show customers what a listener / LB solution looks like.
source is merged and tagged, waiting for next puddle build.
The root cause of the failover we are seeing is due to the ruby Stomp::Connection object being cached/reused, which is fine and actually preferred in most scenarios. However, for the failover scenario the stomp client assumes the connection for the first message it's sending after a failover is healthy and so the message gets lost. A patch to reinitialize the ruby stomp connection will be submitted shortly.
Re-test this bug with 2.2/2014-11-20.1, FAIL.
Firstly, in the latest puddle(2.2/2014-11-20.1), the latest rubygem-openshift-origin-routing-activemq-0.6.1.1-1.el6op is not included into this puddle.
Secondly, for rubygem-openshift-origin-routing-daemon-0.17.1.2-1.el6op, it introduced some new bugs, pls refer to the following bugs for more details, and these bugs are blocking this bug's verification.
Sorry, somehow I must have failed to attach the build. It will make it into today's puddle.
Re-test failover with latest puddle 2.2/2014-11-24.3, it works well when at least one running activemq is existing, but once there is no any running activemq, routing daemon will not reconnect even if activemq come back, pls refer to https://bugzilla.redhat.com/show_bug.cgi?id=1167707 for more detail, so I think the new bug also is blocking this bug's verification.
All the blocked bug is fixed, so I think this bug could be moved to ON_QA now.
After BZ#1169324 is fixed, will verify this bug.
All the blocking bug is fixed in rubygem-openshift-origin-routing-daemon-0.20.2.5-1.el6op.noarch, so move this bug to verified status, but still need note that BZ#1168994 maybe bring some troubles.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.