Due to a race condition in the JBoss EWS cartridge control script, the parent EWS process was killed before the child processes in certain situations, causing the control script to report an error. This bug fix improves the fallback process clean-up logic to handle this error, and the issue no longer occurs as a result. A cartridge upgrade is required after applying this fix.
Comment 1Brenton Leanhardt
2014-08-01 14:12:42 UTC
Upstream commit:
commit c5d33d05525f4e0b3651a17945874a15d276175e
Author: Ben Parees <bparees>
Date: Wed Jul 30 23:30:10 2014 -0400
always meet control error when restartstop a jbossews scalable app with
medium or large gear size
https://bugzilla.redhat.com/show_bug.cgi?id=1124361
Verify this bug with openshift-origin-cartridge-jbossews-1.22.3.5-1.el6op.noarch.
Related code has been merged in.
On node, modify /etc/openshift/resource_limits.conf to the same configuration with resource_limits.conf.medium_m3.xlarge on devenv. Restart mcollective service.
1. Create scalable jbossews-2.0 app
2. Restart and stop/start the app. No error happened.
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.
http://rhn.redhat.com/errata/RHBA-2014-1095.html
Upstream commit: commit c5d33d05525f4e0b3651a17945874a15d276175e Author: Ben Parees <bparees> Date: Wed Jul 30 23:30:10 2014 -0400 always meet control error when restartstop a jbossews scalable app with medium or large gear size https://bugzilla.redhat.com/show_bug.cgi?id=1124361