Why do I need to restart Apache and Tomcat every time a java file is change
843835Jul 29 2002 — edited Sep 25 2003If a java file is changed and complied the changes are not reflected if Tomcat is not restarted.
The settings in server.xml are as:
<!-- Tomcat Manager Context -->
<Context path="/manager" docBase="manager" debug="0" privileged="true"/>
<Context path="/cf" docBase="cf" debug="0" reloadable="false"/>
Here "cf" is my Application folder under webapps. The reloadable property when set to "true" for standalone Tomcat on Windows98 reflects the changes for compiled java files without restarting Tomcat. But on Linux 7.1 with Apache 1.3.19 and Tomcat 4.0.3 this is not working.
Also tried out with Manager Application of tomcat-users.xml with reloadable="false" as well as reloadable="true",
But when I reload the application using the command
http://servername:8080/manager/reload?path=/appli.name
It tells me that the application is reloaded but changes in the java file are still not reflected.
Also when reloaded through Manager Servlet, Only my load-on-startup servlet is reloaded, but other java classes are not.
Is it neccessary to execute this reload command from the server itself. I m executing it from a remote m/c. and have mapped the application with a domain name virtually.
Is it the case with Tomcat on Linux with Apache. Or is something going wrong on my part.
Can someone Help out plz.
Regards,
Rupali