|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Windows XP SP2, Java 4.4.2_07, Tomcat 5.30
|
|
| Resolution Date: |
25/May/05 07:53 AM
|
|
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
|
|
Description
|
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 |
Show » |
|
Bug
Resolved
Major
(re)Deployed portlet application wars not always (re)deployed