1 of 1 people found this helpful
From server perspective a deployment failure is no reason to stop the server complete as other applications might able to run.
You might wrap the start script and start a second process to check whether you see the startmessage and no errors. If you have errors you can send a kill signal to the JBoss process or otherwhise end the process.
Do you have any idea how to acheive this ? some sample or something can be helpful.
If you look into the run.sh (unix) you find how to start processes (JBoss) in background and how to handle the signals. If you check the loggiles after start the process you can look for the "started ..." message and whether you see problems before that.
In case of problems you can stop JBoss and exit.
For Windows I do not have an idea as I'm not familiar with the *.bat file programming.
Thanks Fink for your hints