Bug 1223877 - [GSS](6.4.z) jboss-cli.bat exits with wrong return code
Summary: [GSS](6.4.z) jboss-cli.bat exits with wrong return code
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.0
Hardware: Unspecified
OS: Windows
low
low
Target Milestone: CR1
: EAP 6.4.12
Assignee: Brad Maxwell
QA Contact: Petr Kremensky
URL:
Whiteboard: eap6412-proposed
Depends On:
Blocks: eap6412-payload
TreeView+ depends on / blocked
 
Reported: 2015-05-21 15:23 UTC by Vincent Mooser
Modified: 2019-09-12 08:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 13:09:38 UTC
Type: Bug

Attachments (Terms of Use)
jboss-cli.bat (2.22 KB, text/plain)
2015-11-24 21:43 UTC, Brad Maxwell 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3578 0 Major Resolved jboss-cli.bat always exits with return code 0 even after a cli failure 2017-02-14 13:56:33 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.