Bug 1147194
| Summary: | JBoss CLI --connect option prints exception on connection refused | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Bryan Parry <bparry> | ||||
| Component: | CLI | Assignee: | jboss-set | ||||
| Status: | CLOSED EOL | QA Contact: | Petr Kremensky <pkremens> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.3.1 | CC: | brian.stansberry, cdewolf | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-08-19 12:46:22 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: | |||||||
| Attachments: |
|
||||||
Created attachment 941934 [details] connect stacktrace Description of problem: While the server is not running, if jboss-cli.sh is started with the --connect option (or the -c variant), the connection fails and a stacktrace is printed. The stack trace should not be printed, just an error displayed. It should behave the same way when the "connect" command is issued on startup and it fails. Version-Release number of selected component (if applicable): Red Hat JBoss Enterprise Application Platform - Version 6.3.1.GA How reproducible: Yes Steps to Reproduce: 1. Log on to the server where JBoss EAP is installed, and cd to $EAP_HOME/bin 2. Stop the EAP server, if necessary 3. ./jboss-cli.sh --connect Actual results: The connection fails, and a stacktrace is printed. See attachment for stacktrace. Expected results: The connection fails, and the following error is printed: The controller is not available at localhost:9999: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9999. The connection failed: JBAS012174: Could not connect to remote://localhost:9999. The connection failed: Connection refused Additional info: To demonstrate the expected behavior, execute the following while the server is stopped: ./jboss-cli.sh connect