One more log:
2011-12-12 00:52:15 org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1$
2011-12-12 00:52:16 org.apache.tomcat.util.digester.Digester endElement
WARNING: No rules found matching 'Server/Service/Context'.
2011-12-12 00:52:16 org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting
property 'debug' to '0' did not find a matching property.
2011-12-12 00:52:16 org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
Setting property 'debug' to '0' did not find a matching property.
2011-12-12 00:52:16 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
2011-12-12 00:52:16 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1020 ms
2011-12-12 00:52:16 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
2011-12-12 00:52:16 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
2011-12-12 00:52:17 org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO: validateJarFile(/var/www/torun/WEB-INF/lib/servletapi-2.2.jar) -
jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig
deployDescriptor
INFO: Deploying configuration descriptor host-manager.xml
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig
deployDescriptor
INFO: Deploying configuration descriptor manager.xml
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory docs
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory ROOT
2011-12-12 00:52:18 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory examples
2011-12-12 00:52:18 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
2011-12-12 00:52:18 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
2011-12-12 00:52:18 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/10 config=null
2011-12-12 00:52:18 org.apache.catalina.startup.Catalina start
INFO: Server startup in 1976 ms
2011-12-12 00:53:09 org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
2011-12-12 00:53:10 org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
2011-12-12 00:53:10 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-12-12 00:53:11 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-12-12 00:53:12 org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 1 instance(s) to be deallocated
2011-12-12 00:53:12 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 requests to finish by using the unloadDelay
attribute of the standard$
2011-12-12 00:53:12 org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
It is probly Tomcat + Xen (KVM) + Intel (?) releted problem. I install
tomcat from 5 to 7 on diferent VPS's, always have the same result but
always i have Xen or KVM and Intel CPU, old serwer has AMD cpu and all
works great (and some older version of Xen also), but on new Xen or KVM
based VPS i always have the same problem. But when i run XEN machine
with Windows 8 and run on it VirtuaBox and starts new 32 bit CentOS all
work great (but i have virtualization on virtualized machine ;) ). Its
realy strange problem, and have no idea how to solve it.
Best wishes,
Marcin
On 29.11.2011 23:05, Christopher Schultz wrote:
-----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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
