Description
We have a problem here when starting jboss-cli.sh from a recent jboss-7.3.3 here and I think it is related to aesh.
Sometimes the CLI does not start and the Error message is:
java.io.FileNotFoundException: /home/jboss/.aesh_aliases (No such file or directory): /home/jboss/.aesh_aliases (No such file or directory)
This looks much like a parallelization problem. We are using ansible to set up 4 different jboss servers simultaniously during our deployment so I gues when you start all 4 cli's at the same time like so:
/opt2/jboss1/bin/jboss_cli.sh && /opt2/jboss2/bin/jboss_cli.sh && /opt2/jboss3/bin/jboss_cli.sh && /opt2/jboss4/bin/jboss_cli.sh
it sometimes happens that the first cli somehow has deleted .aesh_aliases when another cli is trying to open it.
As I think a shell should be startable at any given time this exception should be handled that more appropriate than just not letting the shell fail.