Stopping the server via the console view is the same as terminating the process. It's equivilent to kill -9 pid in a *nix environment. It does not properly shut down the server.
Stopping via the view is where it actually requests the server to shut itself down properly... which naturally takes a bit longer.
As for full publish, more details of your use case would be helpful. WTP / web / ear projects? single deployed files? project archives deployment? Which?
Thanks for the reply!! When you say properly shuts down the server, what's the difference between killing it and shutting it down properly? Memory leaks or something??
We are deploying an Ear file, I just went to do a full publish to paste the stack trace for you and viola! it worked. Must have changed something from when it was giving me this problem till now. Oh well. Thanks for the reply.. if the problem with the full publish comes back I'll post it here.
Darryl A. Sibeon