axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rainer Menzner (JIRA)" <>
Subject [jira] Created: (AXIS2-1596) Re-Deployment is somewhat unreliable.
Date Fri, 03 Nov 2006 11:39:19 GMT
Re-Deployment is somewhat unreliable.

                 Key: AXIS2-1596
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: deployment
    Affects Versions: 1.1
         Environment: Win XP SP2, Mozilla Firefox, Tomcat 5.5.20.
            Reporter: Rainer Menzner
            Priority: Minor

When recompiling a service and re-deploying the resulting archive, it can happen that the
status of the tomcat / webservice is not exactly predictable. Alas, this effect is not reproducable.
I encountered the following two situations:

1) After changing the function body of a webservice method, recompiling and re-deploying (at
least the archive file has been copied!), the webservice method executed the previous code.

2) After renaming a function, the page http://localhost:8080/axis2/services/listServices showed
both the former function at the new function.

Restarting tomcat solves these problems. However, according to what is documented, one should
rely on deployment by coyping the archive file.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message