Hello Santosh. Thank you for your reply.
I do use the shell and command ctrl+C to stop an instance. No issues here.
The files .dodeploy and .isdeploying sat in the folder for 10 minutes and I finally deleted both of them manually, then restarted the Jboss and the war file was deployed without and issue.
This doen't seem to be a good workaround/solution! I need to understand and resolve this so I can plan for automating the Jboss start-up process without worring about what happens to the deployment.
Any ideas as to why the .dodeploy and .isdeploying sat in the folder without a successful deployment? I would appreciate your assistance.