-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR11
-
None
-
Regression
-
-
-
-
-
-
-
Not Required
CLI returns "0" if EAP is not started
By convention, an 0 indicates success. But CLI is unable to connect to EAP, it is not success.
This is regression against EAP 7.1.0.DR10, EAP 7.0.0 and EAP 6.4.0.
This issue is caused by https://github.com/wildfly/wildfly-core/pull/2051/files
DR11:
[mkopecky@dhcp-10-40-5-65 bin]$ ./jboss-cli.sh -c Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused [mkopecky@dhcp-10-40-5-65 bin]$ echo $? 0 [mkopecky@dhcp-10-40-5-65 bin]$
DR10:
[mkopecky@dhcp-10-40-5-65 bin]$ ./jboss-cli.sh -c Failed to connect to the controller: The controller is not available at localhost:9990: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: WFLYPRT0053: Could not connect to remote+http://localhost:9990. The connection failed: Connection refused [mkopecky@dhcp-10-40-5-65 bin]$ echo $? 1 [mkopecky@dhcp-10-40-5-65 bin]$
- is cloned by
-
-
- Resolved
-
- is incorporated by
-
JBEAP-8294 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta2
-
- Verified
-
