Bug 1223877

Summary: [GSS](6.4.z) jboss-cli.bat exits with wrong return code
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Vincent Mooser <vmo>
Component: CLIAssignee: Brad Maxwell <bmaxwell>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: low Docs Contact:
Priority: low    
Version: 6.4.0CC: bmaxwell, brian.stansberry, cdewolf, ihradek, jboss-set, jtruhlar, msochure, ppalaga, smatasar
Target Milestone: CR1   
Target Release: EAP 6.4.12   
Hardware: Unspecified   
OS: Windows   
Whiteboard: eap6412-proposed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:09:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1375585    
Attachments:
Description Flags
jboss-cli.bat none

Description Vincent Mooser 2015-05-21 15:23:48 UTC 
Description of problem:
jboss-cli.bat does not exit with correct return code when calling it from a wrapper script (written in Python or bash/cygwin for example).  It always exits with 0, even if the operation failed. This problem has been addressed in Wildfly (https://issues.jboss.org/browse/WFLY-3578)

Version-Release number of selected component (if applicable):
Confirmed on EAP 6.3.x and 6.4.0
Comment 3 Shay Matasaro 2015-10-01 13:29:46 UTC 
requested for next EAP CP
Comment 5 Brad Maxwell 2015-11-24 21:43:25 UTC 
Created attachment 1098426 [details]
jboss-cli.bat
Comment 6 Mike McCune 2016-03-28 22:21:14 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 8 Ivo Hradek 2016-11-15 08:22:33 UTC 
Verified with EAP 6.4.12.CP.CR1;
Comment 9 Petr Penicka 2017-01-17 13:09:38 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.