Hi Sri. Thank you for replying. Your notes were very helpful.
1- The Windows Server has 3 instances of the Jboss (Development = C:\Jboss, TEST = D:\TEST_Jboss, Production = D:\PROD_Jboss).
2- The example I had provided is the D:\TEST_Jboss\standalone\deployments
As you noticed in the logs, I had created a folder called Archive under D:\TEST_Jboss\standalone\deployments to keep older versions of the WAR files. After reading your response, I realized that Jboss maybe scanning the /deployment folder and all subfolders. So I removed the Archive folder. Started this TEST instance and the deployment succeeded without errors (Thank you very much for pointing that our to me).
Question 1- Why would the deployment succeed after deleting the ".failed" file in the D:\TEST_Jboss\standalone\deployments without touching the files in the Archive folder?
More importantly, what happens now when I stop the TEST instance (The deployed file remains in the D:\TEST_Jboss\standalone\deployments folder) and attempt to restart the Jboss? I just tried this and noticed that the deployed war file extension changed to ".dodeploy" and a new file got created with ".isdeploying" extension. Nothing else happens. The site is not up.
Question 2- What's the recommended method of stopping the Jboss instance so that the existing deployed WAR file is removed making it possible for the next Jboss Start-up to deploy the WAR file without errors and issues?
I have not modified the security/permissions. I'll stay with one change for now and monitor the system for few days and see if I see other issues.