|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The initial issue is not an issue in Jenkins or in the deploy plugin.
It is an issue coming from Tomcat:
"Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: FAIL - Failed to deploy application at context path /blogic"
and in Tomcat log:
INFO: Deploying web application archive blogic.war
08.07.2011 12:37:14 org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(D:\blogic\webapps\blogic\WEB-INF\lib\servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
So this was probably a problem in the war file of the webapp (servlet-api.jar should not be included in the war file).
The other cases given in the comments were about problems when Tomcat undeploys, for example with resources and files not closed by the webapp: in fact, the webapp should properly close resources in a "destroy" method.
So resolving this issue as "not a defect".