(re)Deployed portlet application wars not always (re)deployed
-------------------------------------------------------------
Key: JS2-261
URL: http://issues.apache.org/jira/browse/JS2-261
Project: Jetspeed 2
Type: Bug
Components: Deployment
Versions: 2.0-M2, 2.0-M3
Environment: Windows XP SP2, Java 4.4.2_07, Tomcat 5.30
Reporter: Scott T Weaver
Fix For: 2.0-M3, 2.0-FINAL
More often than not (in my experience) newly/redeployed wars are not being
picked up by Tomcat if the war is in the Jetspeed deploy directory prior to
starting Tomcat. Touching the war once it has been copied to the Tomcat
webapps directory will then cause Tomcat to deploy the newer war file. IMO,
this is more of a tomcat issue than a J2 one. An easy resolution could be to
possibly delay the startup of the deployment service ~10-15 seconds prior to
inital container startup as I feel this is more of a timing issue than anything
else.
-Scott
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
