DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7026>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7026 AutoDeploy works bad Summary: AutoDeploy works bad Product: Tomcat 3 Version: 3.3 Release Candidate 1 Platform: PC OS/Version: Linux Status: NEW Severity: Critical Priority: Other Component: Config AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] My environment : Tomcat 3.3a (with apache 1.3.22/mok_jk/ajp13 or with tomcat:8080) Java HotSpot(TM) Server VM (build 1.3.1_02-b02, mixed mode) Linux 2.4.16 i686 with AutoDeploy : <AutoDeploy source="webapps" target="webapps" redeploy="true" /> and <ReloadInterceptor fullReload="true" /> My application (/AppliTest) works in this context. I modify the sources, re-compile them and deploy them in $TOMCAT_HOME/webapps (which is a link on /usr2/webapps). Without re-starting tomcat, I see my modifications BUT the old native_threads java are still here and new ones are created. So, if I re-start this operation some times, I have more and more native_threads java and, at a moment, my system is down (I have to re-boot) because I can't do any fork !!! So, this functionality is a little good (?) for developpement (because I can restart server after some modifications and before it is too late), because it can't be acceptable for production servers . So , is there other solution in Tomcat (for production servers)? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
