You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by si...@8host.pl on 2011/12/12 01:29:38 UTC
Re: Tomcat 5.5 crashes after changing server IP
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, sirwiz@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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 5.5 crashes after changing server IP
Posted by Pid <pi...@pidster.com>.
On 12/12/2011 12:02, André Warnier wrote:
> sirwiz@8host.pl wrote:
>>>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>>>
>>> I really have no idea how you come to that conclusion.
>>
>> Like i said when i install Windows 8 on Xen machine, starts Virtuabox
>> on it and new 32bit Centos, tomcat and my api works perfectly. It was
>> running for a 2 years on AMD procesor (with the same config files) and
>> it works like charm also. Problem starts when we switch to new Intel
>> machine. I also try to install the same version of xen on AMD server
>> and it works, that only dont work on xen or kvm. Also i dowload whole
>> Xen disk image and run it on different intel procesor on virtuabox
>> (Windoiws 7) and the same error. Its realy strange situation when i
>> have to virtualize 2 systems to make it work ;). When i convert
>> working virtuabox machine to Xen image, i have the same error.
Correlation != causation
Have you fixed the other errors in your config?
p
> It seems really unclear what all of this has to do with Tomcat.
> Tomcat is Java code. It runs under a JVM, and uses that JVM's code for
> anything to do with the interface to the underlying OS or hardware. So
> it should not make an iota of difference to Tomcat under which OS and
> machine it is running.
> On the other hand, the /JVM/ which you are using may have problems, but
> again that has nothing to do fundamentally with Tomcat.
>
>>
>>
>>>> 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.
>>>
>>> Fix one thing at a time. Start with your config.
>>
>> It was log from "oryginal" Tomcat instalation, on new install we have
>> only AJP stops and Memory Leak.
>>
>
> Then provide the new log, or do you just want us to keep guessing ?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
--
[key:62590808]
Re: Tomcat 5.5 crashes after changing server IP
Posted by André Warnier <aw...@ice-sa.com>.
sirwiz@8host.pl wrote:
>>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>>
>> I really have no idea how you come to that conclusion.
>
> Like i said when i install Windows 8 on Xen machine, starts Virtuabox on
> it and new 32bit Centos, tomcat and my api works perfectly. It was
> running for a 2 years on AMD procesor (with the same config files) and
> it works like charm also. Problem starts when we switch to new Intel
> machine. I also try to install the same version of xen on AMD server and
> it works, that only dont work on xen or kvm. Also i dowload whole Xen
> disk image and run it on different intel procesor on virtuabox (Windoiws
> 7) and the same error. Its realy strange situation when i have to
> virtualize 2 systems to make it work ;). When i convert working
> virtuabox machine to Xen image, i have the same error.
It seems really unclear what all of this has to do with Tomcat.
Tomcat is Java code. It runs under a JVM, and uses that JVM's code for anything to do with
the interface to the underlying OS or hardware. So it should not make an iota of
difference to Tomcat under which OS and machine it is running.
On the other hand, the /JVM/ which you are using may have problems, but again that has
nothing to do fundamentally with Tomcat.
>
>
>>> 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.
>>
>> Fix one thing at a time. Start with your config.
>
> It was log from "oryginal" Tomcat instalation, on new install we have
> only AJP stops and Memory Leak.
>
Then provide the new log, or do you just want us to keep guessing ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 5.5 crashes after changing server IP
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
SirWiz,
On 12/12/11 6:26 AM, sirwiz@8host.pl wrote:
>>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>>
>> I really have no idea how you come to that conclusion.
>
> Like i said when i install Windows 8 on Xen machine, starts
> Virtuabox on it and new 32bit Centos, tomcat and my api works
> perfectly. It was running for a 2 years on AMD procesor (with the
> same config files) and it works like charm also.
So, you are running a doubly-virtualized environment? That seems ...
unnecessary.
- -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/
iEYEARECAAYFAk7mXugACgkQ9CaO5/Lv0PCMSQCfd71oa1BjWJMrj3nmPC5lo3SL
wbYAoKz4/5McJD6sw7dWkDxzJOaM+cO/
=vdWF
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 5.5 crashes after changing server IP
Posted by si...@8host.pl.
>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>
> I really have no idea how you come to that conclusion.
Like i said when i install Windows 8 on Xen machine, starts Virtuabox
on it and new 32bit Centos, tomcat and my api works perfectly. It was
running for a 2 years on AMD procesor (with the same config files) and
it works like charm also. Problem starts when we switch to new Intel
machine. I also try to install the same version of xen on AMD server and
it works, that only dont work on xen or kvm. Also i dowload whole Xen
disk image and run it on different intel procesor on virtuabox (Windoiws
7) and the same error. Its realy strange situation when i have to
virtualize 2 systems to make it work ;). When i convert working
virtuabox machine to Xen image, i have the same error.
>> 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.
>
> Fix one thing at a time. Start with your config.
It was log from "oryginal" Tomcat instalation, on new install we have
only AJP stops and Memory Leak.
Best wishes
Marcin
On 12.12.2011 09:03, Pid wrote:
> On 12/12/2011 00:29, sirwiz@8host.pl wrote:
>> 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'.
>
> You can't define a Context directly under Service in server.xml, it
> must
> be inside a Host.
>
> You should avoid defining the Context in server.xml at all. Instead,
> put it in 'torun/META-INF/context.xml'
>
>> 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.
>
> There is no debug property on Host.
>
>> 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.
>
> There is no debug property on Context.
>
>> 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
>
> You have a JAR in your application that you should not have.
>
> If you have published /var/www/ (or /var/www/torun) as an Apache
> HTTPD
> DocumentRoot you are increasing the risk of exposing data that should
> be
> protected, because Apache HTTPD will bypass Tomcat controls.
>
>> 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
>
> This looks like a normal stop.
>
>> 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
>
> A request was taking a long time to process & was still running when
> the
> server stopped.
>
>> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
>
> I really have no idea how you come to that conclusion.
>
>
>> 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.
>
> Fix one thing at a time. Start with your config.
>
>
> p
>
>
>> On 29.11.2011 23:05, Christopher Schultz wrote:
>> Sirwiz,
>>
>> On 11/29/11 11:51 AM, sirwiz@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
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 5.5 crashes after changing server IP
Posted by Pid <pi...@pidster.com>.
On 12/12/2011 00:29, sirwiz@8host.pl wrote:
> 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'.
You can't define a Context directly under Service in server.xml, it must
be inside a Host.
You should avoid defining the Context in server.xml at all. Instead,
put it in 'torun/META-INF/context.xml'
> 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.
There is no debug property on Host.
> 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.
There is no debug property on Context.
> 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
You have a JAR in your application that you should not have.
If you have published /var/www/ (or /var/www/torun) as an Apache HTTPD
DocumentRoot you are increasing the risk of exposing data that should be
protected, because Apache HTTPD will bypass Tomcat controls.
> 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
This looks like a normal stop.
> 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
A request was taking a long time to process & was still running when the
server stopped.
> It is probly Tomcat + Xen (KVM) + Intel (?) releted problem.
I really have no idea how you come to that conclusion.
> 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.
Fix one thing at a time. Start with your config.
p
> On 29.11.2011 23:05, Christopher Schultz wrote:
> Sirwiz,
>
> On 11/29/11 11:51 AM, sirwiz@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
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
--
[key:62590808]