That's probably because you configured your datasource jdbc/juddiDB in the global context instead of in a specific (juddi?) webapp context. Because all webapps have access to global context, a change in global context affects all webapps and tomcat restarts all webapps.
En l'instant précis du 21/08/07 09:04, Marco Schwarz s'exprimait en ces termes: > Hi, I'm new in the list and I begin using apache-tomcat-5.5.23 with juddi. > > My question: > When I change a parameter JNDI (jdbc/juddiDB) in the juddy project with > the Administration Tool I see the following log and my session is > invalidate. > > 21.08.2007 08:19:22 org.apache.catalina.startup.HostConfig checkResources > INFO: Undeploying context [/manager] > 21.08.2007 08:19:22 org.apache.catalina.startup.HostConfig checkResources > INFO: Undeploying context [/host-manager] > 21.08.2007 08:19:22 org.apache.catalina.startup.HostConfig checkResources > INFO: Undeploying context [/balancer] > 21.08.2007 08:19:23 org.apache.catalina.startup.HostConfig checkResources > INFO: Undeploying context [/admin] > > Why does tomcat undeploy this webapps? > > Thanks > Marco > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- http://www.noooxml.org/ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
