-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sirwiz,
On 11/29/11 11:51 AM, sir...@8host.pl wrote: > I can run tomcat with examples scripts (i just install t 7.0.23) > and i have this error: > > 2011-11-29 17:38:43 org.apache.coyote.AbstractProtocol start INFO: > Starting ProtocolHandler ["http-bio-8080"] 2011-11-29 17:38:43 > org.apache.coyote.AbstractProtocol start INFO: Starting > ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:38:43 > org.apache.catalina.startup.Catalina start INFO: Server startup in > 645 ms 2011-11-29 17:39:50 org.apache.coyote.AbstractProtocol > pause INFO: Pausing ProtocolHandler ["http-bio-8080"] 2011-11-29 > 17:39:50 org.apache.coyote.AbstractProtocol pause INFO: Pausing > ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:50 > org.apache.catalina.core.StandardService stopInternal INFO: > Stopping service Catalina 2011-11-29 17:39:50 > org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1 > instance(s) to be deallocated 2011-11-29 17:39:51 > org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1 > instance(s) to be deallocated 2011-11-29 17:39:52 > org.apache.catalina.core.StandardWrapper unload INFO: Waiting for 1 > instance(s) to be deallocated 2011-11-29 17:39:52 > org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads SEVERE: The web application [] is still > processing a request that has yet to finish. This is very likely to > create a memory leak. You can control the time allowed for $ > 2011-11-29 17:39:52 org.apache.coyote.AbstractProtocol stop INFO: > Stopping ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52 > org.apache.coyote.AbstractProtocol stop INFO: Stopping > ProtocolHandler ["ajp-bio-8009"] 2011-11-29 17:39:52 > org.apache.coyote.AbstractProtocol destroy INFO: Destroying > ProtocolHandler ["http-bio-8080"] 2011-11-29 17:39:52 > org.apache.coyote.AbstractProtocol destroy INFO: Destroying > ProtocolHandler ["ajp-bio-8009"] > > > Then server stops. That looks like an orderly shutdown of Tomcat. > On old machine it works perfect without any problems. I speak with > my administrator and i get information that this server is a > virtualization on XEN, and with IP they change procesor of hub > machine, but it shouldnt make difrence to xen virtusalization > server. I wouldn't expect Tomcat (or the JVM, really) to get upset with an IP change at runtime, unless you had bound to an interface that suddenly disappeared (like you bind to 10.1.1.10 and suddenly that goes away). My expectation under those circumstances would be that the process just continues and never sees any connections after the IP change. It looks more like your service was intentionally shut down. Are there any other logs? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7VVyYACgkQ9CaO5/Lv0PBTVwCeL+lnxoQV1J2yiYn9F0nsqOLU Zs0AnjuGeBtmSdp7lZFmpz0mznsd/9S5 =sOXj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
