Hi Mike, I posted a bug about this, warp connector shows all sorts of odd behaviour with the manager app. because the way applications are indexed internally to tomcat. Example: you stop on application, then re-install it. When you reinstall it, tomcat gives it a incremented id, yet webapp is still looking for the previous id. The solution to this is to restart apache, the point where mod_webapp indexes the applications.
Regards, James Williamson www.nameonthe.net ----- Original Message ----- From: Mike Johnson <[EMAIL PROTECTED]> To: Tomcat Users List <[EMAIL PROTECTED]> Sent: Wednesday, March 20, 2002 9:02 PM Subject: reloadable doesn't work with warpconnector > > Hi everyone, > > I'm new to Tomcat, so this could be something that I've done > wrong... I've noticed some strange behavior with the warpconnector. > > For example, if I use the manager application to shutdown the root > path (manager/stop?path=/) then the pages are no longer served by the > *standalone* server, but using the warpconnector, they are still > served. > > Also, I have a servlet that is under a path I've set to use > reloadable="true". Accessing that applet through Apache never reflects > a change unless Tomcat is restarted. However the servlet is reloaded > it accessed through the standalone connector. > > Can anybody help me with this? It's been driving me nuts all morning.... > > --- > Tomcat: 4.0.3 > Warpconnector binary from apache.org > jdk 1.3.1 > --- > > Thanks! > > Mike Johnson > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
