You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Sergey V. Udaltsov" <se...@clients.ie> on 2001/11/12 02:45:45 UTC

Update of webapp: does not work with any JVM

Hi all

I have the same old problem with 4.0.1. It does not want to update my
webapp.
What I do:
1. Create some WAR.
2. Install my WAR (with manager webapp, using jar:file:/....)
3. Look at it in a browser. Everything is fine.
4. Uninstall WAR
5. Install the same (same name) WAR with some updated JSPs (so the
timestamps of JSP and WAR files are updated).
6. Look at it in a browser again.
And at this point I still see the old content.:(((

Some time ago, I already reported this problem. There was and idea to
change the JVM from Sun to IBM. I just have done it - and no changes.

BTW, the $TOMCAT4/webapps/myapp still contains old version of all the
stuff I put in WAR.

Any other ideas to check? Any workarounds? I do not want to restart the
tomcat every time (and I do not want to unpack my WAR into
$TOMCAT4/webapps manually).

Cheers,

Sergey

PS BTW, do we have chance to get mod_webapp in RPM for 4.0.1?


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>

RE: Update of webapp: does not work with any JVM

Posted by "Craig R. McClanahan" <cr...@apache.org>.

On 12 Nov 2001, Sergey V. Udaltsov wrote:

> Date: 12 Nov 2001 11:42:31 +0000
> From: Sergey V. Udaltsov <se...@clients.ie>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: RE: Update of webapp: does not work with any JVM
>
> > I had this problem also. The only way I could get Tomcat 4 to update was to
> > decompress the war into a directory in webapps. Then I use the manager to
> > reload my application. It's all in an ant task, which makes it not very
> > painful:
> Thanks a lot for the idea.
>
> > I no longer use Tomcat 4 due to stability issues, I'm using
> > jboss/tomcat3.2.3 bundle which handles hot deployment beautifully. The
> But supports old API only:(
>
> The question to tomcat team: is it registered bug/problem? What are
> perspectives? Does all this mean Tomcat 4.0.1 is not ready yet for
> servlet development environment (only for production:)?
>

Since I don't know what "it" you are speaking of, the only thing I can do
is point you to the bug tracking system and let you tell me if there's a
bug report already there.

  http://nagoya.apache.org/bugzilla/

Use product category "Tomcat 4" to do your search.  It would also be
helpful to reproduce any Tomcat+JBoss bug in stand alone Tomcat before
reporting it -- nobody on the Tomcat development team had anything to do
with the JBoss integration links, so any bugs introduced by that are going
to have to be addressed to the JBoss team.


> Cheers,
>
> Sergey
>

Craig


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>

RE: Update of webapp: does not work with any JVM

Posted by "Sergey V. Udaltsov" <se...@clients.ie>.
> I had this problem also. The only way I could get Tomcat 4 to update was to
> decompress the war into a directory in webapps. Then I use the manager to
> reload my application. It's all in an ant task, which makes it not very
> painful:
Thanks a lot for the idea.

> I no longer use Tomcat 4 due to stability issues, I'm using
> jboss/tomcat3.2.3 bundle which handles hot deployment beautifully. The
But supports old API only:(

The question to tomcat team: is it registered bug/problem? What are
perspectives? Does all this mean Tomcat 4.0.1 is not ready yet for
servlet development environment (only for production:)?

Cheers,

Sergey


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>

RE: Update of webapp: does not work with any JVM

Posted by Tom Parker <to...@econz.co.nz>.
From: Sergey V. Udaltsov [mailto:sergey.oudaltsov@clients.ie]
> 1. Create some WAR.
> 2. Install my WAR (with manager webapp, using jar:file:/....)
> 3. Look at it in a browser. Everything is fine.
> 4. Uninstall WAR
> 5. Install the same (same name) WAR with some updated JSPs (so the
> timestamps of JSP and WAR files are updated).
> 6. Look at it in a browser again.
> And at this point I still see the old content.:(((

I had this problem also. The only way I could get Tomcat 4 to update was to
decompress the war into a directory in webapps. Then I use the manager to
reload my application. It's all in an ant task, which makes it not very
painful:

 <target name="install" depends="war">
        <unjar src="${build.output.dir}/your_application.war"
dest="/path/to/tomcat/webapps/your_application" overwrite="true"/>
        <exec executable="wget">
            <arg line="-Y off"/>
            <arg line="--http-user username"/>
            <arg line="--http-passwd password"/>
            <arg line="-O -"/>
            <arg
line="http://localhost:8080/manager/reload?path=/your_application"/>
        </exec>
    </target>

This probably doesn't load the applicaton the first time, I had a restart
target which did a remove and an install.

I'm not sure if this was necessary but I also have this in my server.xml

        <Context path="/your_application"
          docBase="/path/to/tomcat/webapps/your_application"
          debug="1"
          reloadable="true"
          trusted="true" >
        </Context>

I no longer use Tomcat 4 due to stability issues, I'm using
jboss/tomcat3.2.3 bundle which handles hot deployment beautifully. The
reloadable attribute looks useful. You might want to try this with a war
file and if that doesn't work, then decompress the war, that does (or did
here) work.

I'm running Sun Java 1.3.1 on Linux (2.2 kernel).


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>