<source> http://localhost:8080/manager/text/reload?path=/examples </source>
Signal an existing application to shut itself down and reload. This can be useful when the web application context IS NOT RELOADABLE and you have updated classes or property files in the <code>/WEB-INF/classes</code> directory or when you have added or updated jar files in the <code>/WEB-INF/lib</code> directory. Context reloadable attribute would need to reflect reloadable=false e.g. <Context path="/petclinic" reloadable="false"> Buona Fortuna, Martin ______________________________________________ Si prega di non alterare o interrompere questa trasmissione...Grazie > Date: Thu, 17 Oct 2013 18:45:30 +0200 > From: edoa...@aspix.it > To: users@tomcat.apache.org > Subject: can't connect to manager application > > My Tomcat (7.0.42) is listening on port 7080 and I have this > conf/tomcat-users.xml in (production server) > > ------- > <tomcat-users> > <role rolename="manager-script"/> > <user username="myname" password="pwd" > roles="manager-script,manager-gui,manager-jmx"/> > </tomcat-users> > ---------- > if I use > > curl -u myname:pwd > http://localhost:7080/manager/text/reload?path=/myApplication > > the response is-------------------------- > <h1>404 Not found</h1> > <p> > The page you tried to access > (/manager/text/reload) > does not exist. > </p> > <p> > The Manager application has been re-structured for Tomcat 7 onwards > and some > of URLs have changed. All URLs used to access the Manager > application should > now start with one of the following options: > </p> > <ul> > <li>/manager/html for the HTML GUI</li> > <li>/manager/text for the text interface</li> > <li>/manager/jmxproxy for the JMX proxy</li> > <li>/manager/status for the status pages</li> > </ul> > <p> > Note that the URL for the text interface has changed from > "/manager" to > "/manager/text". > </p> > <p> > You probably need to adjust the URL you are using to access the Manager > application. However, there is always a chance you have found a bug > in the > Manager application. If you are sure you have found a bug, and that > the bug > has not already been reported, please report it to the Apache > Tomcat team. > </p> > --------------------------------------------------------- > on my local machine all goes well (same tomcat version but on port > 8080), can't figure what is different on production server... where can > I take a look? > > Some release ago (tomcat 7.0.x sorry, I can't be more precise) all was > well also on production server. Maybe i did something wrong during an > update. > > thank you > Edoardo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
