There may be several problems and you are the only one to find out, because you have posted no error messages or other diagnostic output. Take the following as pointers:

- maybe for some commands a terminal is required or wrongly allocated. Search the man pages of ssh for "-n" and/or "-q" and decide if this applies to your situation. In any case you might want to include the -o BatchMode = yes into your ssh-command.

- try an interactive session with the machine where it doesn't work: if the keys are not exchanged and/or if the system is not in your known_hosts file you might experience problems. To avoid the "The authenticity of ... Are you sure you want to continue connecting (yes/no)?"-message you need to set "StrictHostKeyChecking" to "no" in the options.

- specify an explicit user to use in the ssh-call:

Code:

ssh user@remote.host command

will connect as "user" to "remote.host" and then issue "command" as this user. Otherwise you are relying on the user who issed the command on the local host, which may or may not be what you want.

- you use a variable "JBOSS_HOME" without defining it in the script. It might be that you are not running the same initialisation scripts if your session is not interactive. In general it is better to set explicitly in a script what you use and never use relative pathes at all.

There are most probably several more possibilities of what could have gone wrong, but this is all guessing, so the above list is incomplete in nature.

I hope this helps.

bakunin