Don't use a password. Generate a passphrase-less SSH key and push it to your VM.
If you already have an SSH key, you can skip this step…
Just hit Enter for the key and both passphrases:
$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.
Copy your keys to the target server:
$ ssh-copy-id id@server
id@server's password:
Now try logging into the machine, with ssh 'id@server'
, and check-in:
.ssh/authorized_keys
Note: If you don't have .ssh dir and authorized_keys file, you need to create it first
to make sure we haven’t added extra keys that you weren’t expecting.
Finally, check to log in…
$ ssh id@server
id@server:~$
You may also want to look into using ssh-agent
if you want to try keeping your keys protected with a passphrase.
I might be barking up the wrong tree but I've seen a similar problem in 4.2.x where the clasloader compliance was a problem (which affects the order classes are loaded).
We solved it by editing deploy/jboss-web.deployer/META-INF/jboss-service.xml
Change these two lines to true
<attribute name="Java2ClassLoadingCompliance">
false</attribute>
<attribute name="UseJBossWebLoader">
false</attribute>
Best Answer
I was searching the Internet for this answer and could not find it. I recently figured it out and thought I would share. I wrote a linux shell script that works perfectly. Taking the time to deploy while developing from 2-3 minutes to 10 seconds which makes programming so much faster. Here is my script:
first line of the script navigates to the location of your server bin. the second line opens
jboss-cli.sh
and connects to the instance. everything after<<EOF
and beforeEOF
are commands you can send to the jboss-cli.sh program. In this case Iundeploy
my current instance which isFlcErp.ear
then Ideploy
the full location of my project.You then save this file the file with your desired name
"Deploy"
change the permission withchmod 755 Deploy
Then add this file to your path with:
export $PATH = $PATH:/home/samo/bin
to execute file just type filename into terminal