Re: Tomcat autoDeploy problem on Unix

2005-09-13 Thread Sergey Pariev
Hi. Try something like this in your context.xml antiJARLocking="true" antiResourceLocking="false"> I've had similar problems with Tomcat 5.5.x on Linux but the above line works. HTH, Sergey. Ritchie Gillam пишет: 1)I have created the WAR file on Windows and deployed to Solaris but I also

Re: Tomcat autoDeploy problem on Unix

2005-09-13 Thread Ritchie Gillam
1)I have created the WAR file on Windows and deployed to Solaris but I also tried using the Tomcat Manager GUI without any luck. It is interesting to note that when I FTP the WAR file over from the Windows box, both the app directory and the new WAR file disappear. If I FTP the WAR a second t

Re: Tomcat autoDeploy problem on Unix

2005-09-13 Thread Eugeny N Dzhurinsky
On Tue, Sep 13, 2005 at 03:31:37PM +0200, Christoph Kutzinski wrote: > Do you create the WAR file on Windows and deploy to Solaris? > Have you checked that the system clocks are in sync? > Have you checked that the file attributes are ok on Solaris? > Have you tried to "touch" the war file? I coul

Re: Tomcat autoDeploy problem on Unix

2005-09-13 Thread Christoph Kutzinski
Do you create the WAR file on Windows and deploy to Solaris? Have you checked that the system clocks are in sync? Have you checked that the file attributes are ok on Solaris? Have you tried to "touch" the war file? Olena Mitovska wrote: Hi, We have Tomcat 5.5.7 installed on Solaris 9 and the au

Re: Tomcat autoDeploy problem on Unix

2005-09-13 Thread Stas Ostapenko
Hi ! I'm using tomcat-specific ant tasks and very happy :) It's allows you to restart web app without restarting tomcat. Take a look at manager web app came with distribution. http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html#Executing%20Manager%20Commands%20With%20Ant On 9/13/0

Tomcat autoDeploy problem on Unix

2005-09-13 Thread Olena Mitovska
Hi, We have Tomcat 5.5.7 installed on Solaris 9 and the autoDeploy option doesn't work. We have to restart the server every time we redeploy the application so that changes will be seen, and it is unacceptable for us since it is a production server. Here is the excerpt from our server.xml wh