[jboss-jira] [JBoss JIRA] (WFLY-5885) jconsole.sh should fail fast if JBOSS_HOME is incorrect instead of starting the console with an incorrecdt classpath

[Marek Kopecký (Jira)]

     [ https://issues.jboss.org/browse/WFLY-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Kopecký updated WFLY-5885:
--------------------------------
    Description: 
If {{$JBOSS_HOME}} is incorrectly set, we get a vague WARNING message when the script starts, but jconsole is run and shows the GUI window.  This is misleading, because jconsole won't have the correct classpath and won't be able to connect to Wildfly, leading to an ambiguous "Cannot connect" error.

{{jconsole.sh}} should fail fast if it cannot find the {{jboss-cli-client.jar}} and avoid this entire confusion.

---

Steps to reproduce:
# export JBOSS_HOME=/no/existing/path
# ./standalone.sh

  was:
If {{$JBOSS_HOME}} is incorrectly set, we get a vague WARNING message when the script starts, but jconsole is run and shows the GUI window.  This is misleading, because jconsole won't have the correct classpath and won't be able to connect to Wildfly, leading to an ambiguous "Cannot connect" error.

{{jconsole.sh}} should fail fast if it cannot find the {{jboss-cli-client.jar}} and avoid this entire confusion.



> jconsole.sh should fail fast if JBOSS_HOME is incorrect instead of starting the console with an incorrecdt classpath
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5885
>                 URL: https://issues.jboss.org/browse/WFLY-5885
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: JMX, Scripts
>            Reporter: Cosmin Stroe
>            Priority: Minor
>
> If {{$JBOSS_HOME}} is incorrectly set, we get a vague WARNING message when the script starts, but jconsole is run and shows the GUI window.  This is misleading, because jconsole won't have the correct classpath and won't be able to connect to Wildfly, leading to an ambiguous "Cannot connect" error.
> {{jconsole.sh}} should fail fast if it cannot find the {{jboss-cli-client.jar}} and avoid this entire confusion.
> ---
> Steps to reproduce:
> # export JBOSS_HOME=/no/existing/path
> # ./standalone.sh



--
This message was sent by Atlassian Jira
(v7.12.1#712002)