servlet load-on-startup/ causes TC 5.0.3 to hang on startup
Tomcat 5.0.3 on W2K hangs on startup whenever I deploy an app whose web.xml has a servlet definition that contains a load-on-startup element, either with or without a number. This happens consistently on my TC installation, which has unpackWARs set to true. Has anyone seen this behavior before? Thanks, Mike -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem reloading unpacked web app with Tomcat 5.0.3
I'm now trying to redeploy the app by firest removing it with a remove request to the tomcat manager app. This works as long as there are no jar files in the app's WEB-INF/lib directory. The remove request deletes the app's directory from webapps, and the deploy task recreates the directory. However, if the there are jar files in the lib directory, the remove request does not remove the directory completely from webapps. WEB-INF/lib/*.jar still remain. If I try to remove the jar files manually, I get a sharing violation error. It seems that a remove request to Tomcat should always delete the directory from webapps whether or not the app contains jar files. Is this a Tomcat bug? If not, aside from restarting Tomcat, how I do tell Tomcat to release the app's jar files? Thanks, Mike Michael Woinoski wrote: I've refined the problem somewhat. I think I need to supply a Context with reloadable set to true. So how do I do that with an expanded app? If I copy a context definition (Context reloadable=true... /) to webapps, Tomcat seems to ignore it. I seem to remember reading that the context definition could be stored in the app's META-INF dir, so I set Tomcat's unpackWARs to true and tried the Ant deploy task again, but again the context definition was ignored. thanks, Mike Michael Woinoski wrote: I need to deploy a web app as an unpacked directory structure (the app needs to be able write a file to its WEB-INF). I also need to automate the deployment and reloading using Ant. So far, I've tried a few things: 1. setting unpackWARs in server.xml to true and copying the war file to the webapps dir 2. copying the expanded directory structure directly in webapps In both cases, the app deployment is successful initially. However, when I make changes (update the war file for case 1 or update the app's classes in case 2) Tomcat does not update the application (i.e., the class files are not reloaded.) The Ant reload task gives errors in both cases. I tried to undeploy and deploy the app using the Ant undeploy task but the undeploy also gave errors in both cases (IncompatibleClassChangeError). However, I can remove the app with the gui app manager. autoDeploy and liveDeploy are both set to true for the Host. Is there something else I need to do to notify Tomcat to reload the class files after modifications? Or is there another way to deploy the expanded app so it will be reloaded automatically? Thanks, Mike -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem reloading unpacked web app with Tomcat 5.0.3
I've refined the problem somewhat. I think I need to supply a Context with reloadable set to true. So how do I do that with an expanded app? If I copy a context definition (Context reloadable=true... /) to webapps, Tomcat seems to ignore it. I seem to remember reading that the context definition could be stored in the app's META-INF dir, so I set Tomcat's unpackWARs to true and tried the Ant deploy task again, but again the context definition was ignored. thanks, Mike Michael Woinoski wrote: I need to deploy a web app as an unpacked directory structure (the app needs to be able write a file to its WEB-INF). I also need to automate the deployment and reloading using Ant. So far, I've tried a few things: 1. setting unpackWARs in server.xml to true and copying the war file to the webapps dir 2. copying the expanded directory structure directly in webapps In both cases, the app deployment is successful initially. However, when I make changes (update the war file for case 1 or update the app's classes in case 2) Tomcat does not update the application (i.e., the class files are not reloaded.) The Ant reload task gives errors in both cases. I tried to undeploy and deploy the app using the Ant undeploy task but the undeploy also gave errors in both cases (IncompatibleClassChangeError). However, I can remove the app with the gui app manager. autoDeploy and liveDeploy are both set to true for the Host. Is there something else I need to do to notify Tomcat to reload the class files after modifications? Or is there another way to deploy the expanded app so it will be reloaded automatically? Thanks, Mike -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem reloading unpacked web app with Tomcat 5.0.3
I need to deploy a web app as an unpacked directory structure (the app needs to be able write a file to its WEB-INF). I also need to automate the deployment and reloading using Ant. So far, I've tried a few things: 1. setting unpackWARs in server.xml to true and copying the war file to the webapps dir 2. copying the expanded directory structure directly in webapps In both cases, the app deployment is successful initially. However, when I make changes (update the war file for case 1 or update the app's classes in case 2) Tomcat does not update the application (i.e., the class files are not reloaded.) The Ant reload task gives errors in both cases. I tried to undeploy and deploy the app using the Ant undeploy task but the undeploy also gave errors in both cases (IncompatibleClassChangeError). However, I can remove the app with the gui app manager. autoDeploy and liveDeploy are both set to true for the Host. Is there something else I need to do to notify Tomcat to reload the class files after modifications? Or is there another way to deploy the expanded app so it will be reloaded automatically? Thanks, Mike -- Mike Woinoski Pine Needle Consulting mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
