At 08:21 AM 8/25/2006, you wrote:
The thing is that we may deploy our application sucessfully. The
missing part is that we do not assure that /hackystat application is
listable, which means Tomcat is still loading Hackystat but we think
it is finished.
My theory is that the exception happens when Tomcat is busy loading
Hackystat application. To ensure that /hackystat is correctly
listed, we can add one more get task to query /hackystat or
hackystat manager either after task hotDeployHackystat or before task
deploySoap.
That is my theory too. I tried a 10 second wait and that didn't work
all the time. So, I agree we could try to query the tomcat manager.
thanks, Aaron
