Thanks for all your responses.
I've also found that bouncing Tomcat can solve this weird problem.
--
View this message in context:
http://www.nabble.com/Getting-%22Exception-invoking-method-check%22-tp18764317p18877802.html
Sent from the Ant - Users mailing list archive at Nabble.com.
Hi,
> Looks like something happening in tomcat; its their stack trace.
>
> Personally, I've found the tomcat tasks fairly tricky to keep
> alive. I prefer to use deploy-by-copy, and just the WAR file straight
> into the tomcat/webapps directory
>
> * it avoids you having to turn on the public man
fphan wrote:
What does this error mean?
Here's the target:
118:
119:
120:
122:
Looks like something happening in tomcat; its their stack trace.
Personally, I've found the tomcat tasks fairly tricky to keep
alive. I prefer to use deploy-by-copy, and just the WAR fi
What does this error mean?
Here's the target:
118:
119:
120:
122:
Here's the verbose output:
/home/yagnika/svn/offline/buildtools/apache-tomcat-5.5.16-deployer/build.xml:121:
FAIL - Encountered exception javax.management.RuntimeOperationsException:
Exception invoking m
