jboss-cli.bat exits with bad return code

Latest response

jboss-cli.bat does not exit with correct return code when calling it from a wrapper script (written in Python or bash/cygwin). It always exits with 0, even if the operation failed. This problem has been addressed in Wildfly (https://issues.jboss.org/browse/WFLY-3578). Is there any plan to fix this in EAP 6.4.x ?

Responses

I believe so, via https://bugzilla.redhat.com/show_bug.cgi?id=1211353 (currently in the ON_QA state). If you want to be sure, I recommend asking in this bug.

At the moment I don't believe this is targeted in EAP 6.4.x. Please raise a support case with us so we can evaluate the issue and see if we can this included in to a CP release for you.

Radek, that BZ points to a JON issue so I don't think this is in JBoss EAP yet.

Thanks
Mustafa

The erratum containing the bug was released last week: https://rhn.redhat.com/errata/RHEA-2015-0947.html. This page indicates that JBEAP 6 was one of the affected products.

I don't see how that bug fix or erratta update for JON has this bug from WFLY in it. I'm not sure what you're looking at. WFLY-3578 has nothing to do with JON, it's a JBoss issue. The erratta you're linking to doesn't contain anything to do with this fix in it https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=37793&product=em&version=3.3&downloadType=patches

Here's the thing: https://issues.jboss.org/browse/WFLY-3578 is mentioned as "See Also" in https://bugzilla.redhat.com/show_bug.cgi?id=1139684. One of the last comments in this bug contains a link to the build system, and here the package fixing the issue is jboss-on-3.3.0.ER04-3.el6. A quick search for open errata containing updated jboss-on packages then revealed RHEA-2015-0947, and this erratum contained tracking bug 1211353 and jboss-on-3.3.0.GA-34.ep6.el6 was attached to it. Maybe that was the wrong route, though.

That basically tells you that BZ-1139684 was hitting WFLY-3578 during their fix for the issue in BZ-1139684. See comment #10. That BZ for EAP was never opened from what I can see and it was fixed upstream in WFLY-3578. Comment #11 explains what they did to workaround the issue in this JON update.

This has not been fixed in JBoss EAP from what I can see and is only fixed upstream in WFLY.