You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Vidyadhar <te...@gmail.com> on 2013/11/01 14:13:06 UTC
Re: Tomcat getting stopped when idle
On 1 Nov 2013 00:52, "Konstantin Kolinko" <kn...@gmail.com> wrote:
>
> 2013/10/31 Vidyadhar <te...@gmail.com>:
> > Hi,
> >
> > We are facing some weird issue in our Tomcat environment. After starting
> > the Tomcat process on one of our Solaris server, process is
automatically
> > getting shutdown after 2-3 minutes if no activity is done through
> > Application deployed in Tomcat.
> >
> > I have observed similar issue in one of following mailing thread where
as
> > user has asked to install a Listener and print a stacktrace when the
stop
> > event
> > happens. I need to know how to install such Listener.
> >
>
> http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html
>
> There are several listeners that have been already configured there. You
can
> use their source code as an example.
>
> > http://www.mail-archive.com/users@tomcat.apache.org/msg84717.html
> >
> > Server version: Apache Tomcat/6.0.16
> > Server built: Jan 28 2008 11:35:29
> > Server number: 6.0.16.0
> > OS Name: SunOS
> > OS Version: 5.10
> > Architecture: sparc
> > JVM Version: 1.6.0_51-b11
> > JVM Vendor: Sun Microsystems Inc.
>
> A recent commercial JRE, but 5,5 years old Tomcat? You may need to read
this:
> http://tomcat.apache.org/security-6.html
>
> >
> >
> > Error in the catalina.out
> >
> > Oct 30, 2013 5:04:56 AM org.apache.coyote.http11.Http11Protocol pause
> > INFO: Pausing Coyote HTTP/1.1 on http-9920
> > Oct 30, 2013 5:04:56 AM org.apache.catalina.connector.Connector pause
> > SEVERE: Protocol handler pause failed
> > java.net.ConnectException: Connection refused
> > at java.net.PlainSocketImpl.socketConnect(Native Method)
> > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
> > at
> > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
> > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
> > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
> > at java.net.Socket.connect(Socket.java:527)
> > at java.net.Socket.connect(Socket.java:476)
> > at java.net.Socket.<init>(Socket.java:373)
> > at java.net.Socket.<init>(Socket.java:216)
> > at
> > org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:486)
> > at
org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:283)
> > at org.apache.jk.server.JkMain.pause(JkMain.java:681)
> > at
> > org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
> > at
> > org.apache.catalina.connector.Connector.pause(Connector.java:1073)
> > at
> > org.apache.catalina.core.StandardService.stop(StandardService.java:563)
> > at
> > org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
> > at org.apache.catalina.startup.Catalina.stop(Catalina.java:628)
> > at
> >
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:671)
>
> Here you already have the stacktrace.
>
> It starts with "CatalinaShutdownHook". It means that JVM was shut down
> by some external force (e.g. a HUP signal). Thus the shutdown hook was
> triggered.
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
Hi Konstantin,
To find out the actual reason we are changing log level to trace. Will keep
you all updated on the same.
Thanks.
Re: Tomcat getting stopped when idle
Posted by Vidyadhar <te...@gmail.com>.
Hi Chris,
On Sat, Nov 2, 2013 at 7:04 PM, Christopher Schultz <
chris@christopherschultz.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Vidyadhar,
>
> On 11/1/13, 11:31 PM, Vidyadhar wrote:
> > Hi Konstantin,
> >
> > On 2 Nov 2013 01:06, "Konstantin Kolinko" <kn...@gmail.com>
> > wrote:
> >>
> >> 2013/11/1 Vidyadhar <te...@gmail.com>:
> >>> On 1 Nov 2013 00:52, "Konstantin Kolinko"
> >>> <kn...@gmail.com>
> > wrote:
> >>>>
> >>>> 2013/10/31 Vidyadhar <te...@gmail.com>:
> >>>>> Hi,
> >>>>>
> >>>>> We are facing some weird issue in our Tomcat environment.
> >>>>> After
> > starting
> >>>>> the Tomcat process on one of our Solaris server, process
> >>>>> is
> >>> automatically
> >>>>> getting shutdown after 2-3 minutes if no activity is done
> >>>>> through Application deployed in Tomcat.
> >>>>>
> >>>>> I have observed similar issue in one of following mailing
> >>>>> thread
> > where
> >>> as
> >>>>> user has asked to install a Listener and print a stacktrace
> >>>>> when the
> >>> stop
> >>>>> event happens. I need to know how to install such
> >>>>> Listener.
> >>>>>
> >>>>
> >>>> http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html
> >>>>
> >>>>
> >>>>
> There are several listeners that have been already configured there.
> > You
> >>> can
> >>>> use their source code as an example.
> >>>>
> >>>>> http://www.mail-archive.com/users@tomcat.apache.org/msg84717.html
> >>>>>
> >>>>>
> >>>>>
> Server version: Apache Tomcat/6.0.16
> >>>>> Server built: Jan 28 2008 11:35:29 Server number:
> >>>>> 6.0.16.0 OS Name: SunOS OS Version: 5.10
> >>>>> Architecture: sparc JVM Version: 1.6.0_51-b11 JVM
> >>>>> Vendor: Sun Microsystems Inc.
> >>>>
> >>>> A recent commercial JRE, but 5,5 years old Tomcat? You may
> >>>> need to read
> >>> this:
> >>>> http://tomcat.apache.org/security-6.html
> >>>>
> >>>>>
> >>>>>
> >>>>> Error in the catalina.out
> >>>>>
> >>>>> Oct 30, 2013 5:04:56 AM
> >>>>> org.apache.coyote.http11.Http11Protocol pause INFO: Pausing
> >>>>> Coyote HTTP/1.1 on http-9920 Oct 30, 2013 5:04:56 AM
> >>>>> org.apache.catalina.connector.Connector pause SEVERE:
> >>>>> Protocol handler pause failed java.net.ConnectException:
> >>>>> Connection refused at
> >>>>> java.net.PlainSocketImpl.socketConnect(Native Method) at
> > java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
> >>>>> at
> >>>>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
> >>>>>
> >>>>>
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
> >>>>> at
> >>>>> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
> >>>>> at java.net.Socket.connect(Socket.java:527) at
> >>>>> java.net.Socket.connect(Socket.java:476) at
> >>>>> java.net.Socket.<init>(Socket.java:373) at
> >>>>> java.net.Socket.<init>(Socket.java:216) at
> >>>>>
> > org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:486)
> >>>>>
> >
> at
> >>> org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:283)
> >>>>>
> >>>
> at org.apache.jk.server.JkMain.pause(JkMain.java:681)
> >>>>> at
> >>>>> org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
> >>>>>
> >>>>>
> at
> >>>>> org.apache.catalina.connector.Connector.pause(Connector.java:1073)
> >>>>>
> >>>>>
> at
> >>>>>
> > org.apache.catalina.core.StandardService.stop(StandardService.java:563)
> >>>>>
> >
> at
> >>>>> org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
> >>>>>
> >>>>>
> at
> > org.apache.catalina.startup.Catalina.stop(Catalina.java:628)
> >>>>> at
> >>>>>
> >>>
> >
> org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:671)
> >>>>
> >>>>
> >
> Here you already have the stacktrace.
> >>>>
> >>>> It starts with "CatalinaShutdownHook". It means that JVM was
> >>>> shut down by some external force (e.g. a HUP signal). Thus
> >>>> the shutdown hook was triggered.
> >>>>
> >>>> Best regards, Konstantin Kolinko
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>
> >>>>
> Hi Konstantin,
> >>>
> >>> To find out the actual reason we are changing log level to
> >>> trace. Will
> > keep
> >>> you all updated on the same.
> >>
> >> What log level?
> >
> > Added .level = fine to understand what is happening.
> >>
> >> Tuning anything on the java side is unlikely to help.
> >>
> >> 1. If shutdown is initiated by ShutdownHook like in the
> >> stacktrace above, it means that JVM died (because of Ctrl+C or
> >> SUGHUP or similar that happened outside of the Java code) or
> >> exited (because of a java.lang.System.exit() call).
> >
> > This is unix environment and I suppose if we execute startup.sh
> > tomcat runs in background.
>
> You might not be able to just run startup.sh and then close your
> connection. Is that what you are doing?
>
> The original list-archives thread you posted explains exactly that
> potential danger.
>
> If you run "startup.sh" and then immediately log out of the terminal
> used to run startup.sh, what happens?
>
It is still in running state. As per my information process runs in
background mode. As of now we have added -Xrs parameter in JVM arguments.
Is there any other way to troubleshoot this issue?
>
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.15 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJSdP9jAAoJEBzwKT+lPKRYvtQQAK6YZHKYKZXdpON6SMyHbpdU
> LzfBwnHPCxUGJ87xvM8bofR/UfWyKEqjcFzvNkRjd76DO4oyRI+kBW3pIvN/W/Zn
> twHnEQvyrF6CZJlMKLUuboAgzfZ0eu6GP77YYIuh2Olt+VaNt7gTAFCg7C370piZ
> h8DwfoTdGahPf9xL5FPCZymNoJIfZac5ugwl62N5V4s4ic0+S1AYCJQRkrMxFTXt
> 9xV7yM1HCRKlfn/y4DdstzB2l0iEMwrfdQHKUxUnG0M/m2o8YNFTz3Ns2hRQLfCG
> EqF4mm03Ou32f/ysMQof8cLodAMfZO0uSGS3/OYnYG2oR+Ved8OOn1KZBFmUvwE0
> U6+0N2oUjqa4qDaHZ9y2lfEX7xySyl8ToY/Y6KCv2In0rdfSMmmZ3jwHRjaUnPk/
> 5Yg1ls9PpBlqS+m4DkVQRcGDQuYrRNeqjcUyPoQyrm5rR8sk2ZoVwc5eMl+cJo0w
> 7UJTceYDccmK7+kUsrJT9pkmhtcelFPILSRimqiiNkYQO+RIq7720F9Y4CQgDZt4
> BFlstq97djtq7hObNdgFxu4GcDTF/kCoBY7ONpAFbHUKgjRTFWaRVmeJh/sHHi0H
> Zmx+bd5GqCEtWeSQgpseL8ppT3halNI3uhRT+18sWEQkAB7uWu2e8s81VOxcxvsO
> jLYo9TzCkTmgCpi/XdTd
> =iIY0
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
--
Regards,
Vidyadhar
Re: Tomcat getting stopped when idle
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Vidyadhar,
On 11/1/13, 11:31 PM, Vidyadhar wrote:
> Hi Konstantin,
>
> On 2 Nov 2013 01:06, "Konstantin Kolinko" <kn...@gmail.com>
> wrote:
>>
>> 2013/11/1 Vidyadhar <te...@gmail.com>:
>>> On 1 Nov 2013 00:52, "Konstantin Kolinko"
>>> <kn...@gmail.com>
> wrote:
>>>>
>>>> 2013/10/31 Vidyadhar <te...@gmail.com>:
>>>>> Hi,
>>>>>
>>>>> We are facing some weird issue in our Tomcat environment.
>>>>> After
> starting
>>>>> the Tomcat process on one of our Solaris server, process
>>>>> is
>>> automatically
>>>>> getting shutdown after 2-3 minutes if no activity is done
>>>>> through Application deployed in Tomcat.
>>>>>
>>>>> I have observed similar issue in one of following mailing
>>>>> thread
> where
>>> as
>>>>> user has asked to install a Listener and print a stacktrace
>>>>> when the
>>> stop
>>>>> event happens. I need to know how to install such
>>>>> Listener.
>>>>>
>>>>
>>>> http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html
>>>>
>>>>
>>>>
There are several listeners that have been already configured there.
> You
>>> can
>>>> use their source code as an example.
>>>>
>>>>> http://www.mail-archive.com/users@tomcat.apache.org/msg84717.html
>>>>>
>>>>>
>>>>>
Server version: Apache Tomcat/6.0.16
>>>>> Server built: Jan 28 2008 11:35:29 Server number:
>>>>> 6.0.16.0 OS Name: SunOS OS Version: 5.10
>>>>> Architecture: sparc JVM Version: 1.6.0_51-b11 JVM
>>>>> Vendor: Sun Microsystems Inc.
>>>>
>>>> A recent commercial JRE, but 5,5 years old Tomcat? You may
>>>> need to read
>>> this:
>>>> http://tomcat.apache.org/security-6.html
>>>>
>>>>>
>>>>>
>>>>> Error in the catalina.out
>>>>>
>>>>> Oct 30, 2013 5:04:56 AM
>>>>> org.apache.coyote.http11.Http11Protocol pause INFO: Pausing
>>>>> Coyote HTTP/1.1 on http-9920 Oct 30, 2013 5:04:56 AM
>>>>> org.apache.catalina.connector.Connector pause SEVERE:
>>>>> Protocol handler pause failed java.net.ConnectException:
>>>>> Connection refused at
>>>>> java.net.PlainSocketImpl.socketConnect(Native Method) at
> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
>>>>> at
>>>>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
>>>>>
>>>>>
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
>>>>> at
>>>>> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
>>>>> at java.net.Socket.connect(Socket.java:527) at
>>>>> java.net.Socket.connect(Socket.java:476) at
>>>>> java.net.Socket.<init>(Socket.java:373) at
>>>>> java.net.Socket.<init>(Socket.java:216) at
>>>>>
> org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:486)
>>>>>
>
at
>>> org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:283)
>>>>>
>>>
at org.apache.jk.server.JkMain.pause(JkMain.java:681)
>>>>> at
>>>>> org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
>>>>>
>>>>>
at
>>>>> org.apache.catalina.connector.Connector.pause(Connector.java:1073)
>>>>>
>>>>>
at
>>>>>
> org.apache.catalina.core.StandardService.stop(StandardService.java:563)
>>>>>
>
at
>>>>> org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
>>>>>
>>>>>
at
> org.apache.catalina.startup.Catalina.stop(Catalina.java:628)
>>>>> at
>>>>>
>>>
> org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:671)
>>>>
>>>>
>
Here you already have the stacktrace.
>>>>
>>>> It starts with "CatalinaShutdownHook". It means that JVM was
>>>> shut down by some external force (e.g. a HUP signal). Thus
>>>> the shutdown hook was triggered.
>>>>
>>>> Best regards, Konstantin Kolinko
>>>>
>>>> ---------------------------------------------------------------------
>>>
>>>>
Hi Konstantin,
>>>
>>> To find out the actual reason we are changing log level to
>>> trace. Will
> keep
>>> you all updated on the same.
>>
>> What log level?
>
> Added .level = fine to understand what is happening.
>>
>> Tuning anything on the java side is unlikely to help.
>>
>> 1. If shutdown is initiated by ShutdownHook like in the
>> stacktrace above, it means that JVM died (because of Ctrl+C or
>> SUGHUP or similar that happened outside of the Java code) or
>> exited (because of a java.lang.System.exit() call).
>
> This is unix environment and I suppose if we execute startup.sh
> tomcat runs in background.
You might not be able to just run startup.sh and then close your
connection. Is that what you are doing?
The original list-archives thread you posted explains exactly that
potential danger.
If you run "startup.sh" and then immediately log out of the terminal
used to run startup.sh, what happens?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJSdP9jAAoJEBzwKT+lPKRYvtQQAK6YZHKYKZXdpON6SMyHbpdU
LzfBwnHPCxUGJ87xvM8bofR/UfWyKEqjcFzvNkRjd76DO4oyRI+kBW3pIvN/W/Zn
twHnEQvyrF6CZJlMKLUuboAgzfZ0eu6GP77YYIuh2Olt+VaNt7gTAFCg7C370piZ
h8DwfoTdGahPf9xL5FPCZymNoJIfZac5ugwl62N5V4s4ic0+S1AYCJQRkrMxFTXt
9xV7yM1HCRKlfn/y4DdstzB2l0iEMwrfdQHKUxUnG0M/m2o8YNFTz3Ns2hRQLfCG
EqF4mm03Ou32f/ysMQof8cLodAMfZO0uSGS3/OYnYG2oR+Ved8OOn1KZBFmUvwE0
U6+0N2oUjqa4qDaHZ9y2lfEX7xySyl8ToY/Y6KCv2In0rdfSMmmZ3jwHRjaUnPk/
5Yg1ls9PpBlqS+m4DkVQRcGDQuYrRNeqjcUyPoQyrm5rR8sk2ZoVwc5eMl+cJo0w
7UJTceYDccmK7+kUsrJT9pkmhtcelFPILSRimqiiNkYQO+RIq7720F9Y4CQgDZt4
BFlstq97djtq7hObNdgFxu4GcDTF/kCoBY7ONpAFbHUKgjRTFWaRVmeJh/sHHi0H
Zmx+bd5GqCEtWeSQgpseL8ppT3halNI3uhRT+18sWEQkAB7uWu2e8s81VOxcxvsO
jLYo9TzCkTmgCpi/XdTd
=iIY0
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat getting stopped when idle
Posted by Vidyadhar <te...@gmail.com>.
Hi Konstantin,
On 2 Nov 2013 01:06, "Konstantin Kolinko" <kn...@gmail.com> wrote:
>
> 2013/11/1 Vidyadhar <te...@gmail.com>:
> > On 1 Nov 2013 00:52, "Konstantin Kolinko" <kn...@gmail.com>
wrote:
> >>
> >> 2013/10/31 Vidyadhar <te...@gmail.com>:
> >> > Hi,
> >> >
> >> > We are facing some weird issue in our Tomcat environment. After
starting
> >> > the Tomcat process on one of our Solaris server, process is
> > automatically
> >> > getting shutdown after 2-3 minutes if no activity is done through
> >> > Application deployed in Tomcat.
> >> >
> >> > I have observed similar issue in one of following mailing thread
where
> > as
> >> > user has asked to install a Listener and print a stacktrace when the
> > stop
> >> > event
> >> > happens. I need to know how to install such Listener.
> >> >
> >>
> >> http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html
> >>
> >> There are several listeners that have been already configured there.
You
> > can
> >> use their source code as an example.
> >>
> >> > http://www.mail-archive.com/users@tomcat.apache.org/msg84717.html
> >> >
> >> > Server version: Apache Tomcat/6.0.16
> >> > Server built: Jan 28 2008 11:35:29
> >> > Server number: 6.0.16.0
> >> > OS Name: SunOS
> >> > OS Version: 5.10
> >> > Architecture: sparc
> >> > JVM Version: 1.6.0_51-b11
> >> > JVM Vendor: Sun Microsystems Inc.
> >>
> >> A recent commercial JRE, but 5,5 years old Tomcat? You may need to read
> > this:
> >> http://tomcat.apache.org/security-6.html
> >>
> >> >
> >> >
> >> > Error in the catalina.out
> >> >
> >> > Oct 30, 2013 5:04:56 AM org.apache.coyote.http11.Http11Protocol pause
> >> > INFO: Pausing Coyote HTTP/1.1 on http-9920
> >> > Oct 30, 2013 5:04:56 AM org.apache.catalina.connector.Connector pause
> >> > SEVERE: Protocol handler pause failed
> >> > java.net.ConnectException: Connection refused
> >> > at java.net.PlainSocketImpl.socketConnect(Native Method)
> >> > at
java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
> >> > at
> >> > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
> >> > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
> >> > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
> >> > at java.net.Socket.connect(Socket.java:527)
> >> > at java.net.Socket.connect(Socket.java:476)
> >> > at java.net.Socket.<init>(Socket.java:373)
> >> > at java.net.Socket.<init>(Socket.java:216)
> >> > at
> >> >
org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:486)
> >> > at
> > org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:283)
> >> > at org.apache.jk.server.JkMain.pause(JkMain.java:681)
> >> > at
> >> > org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
> >> > at
> >> > org.apache.catalina.connector.Connector.pause(Connector.java:1073)
> >> > at
> >> >
org.apache.catalina.core.StandardService.stop(StandardService.java:563)
> >> > at
> >> > org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
> >> > at
org.apache.catalina.startup.Catalina.stop(Catalina.java:628)
> >> > at
> >> >
> >
org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:671)
> >>
> >> Here you already have the stacktrace.
> >>
> >> It starts with "CatalinaShutdownHook". It means that JVM was shut down
> >> by some external force (e.g. a HUP signal). Thus the shutdown hook was
> >> triggered.
> >>
> >> Best regards,
> >> Konstantin Kolinko
> >>
> >> ---------------------------------------------------------------------
> > Hi Konstantin,
> >
> > To find out the actual reason we are changing log level to trace. Will
keep
> > you all updated on the same.
>
> What log level?
Added .level = fine to understand what is happening.
>
> Tuning anything on the java side is unlikely to help.
>
> 1. If shutdown is initiated by ShutdownHook like in the stacktrace
> above, it means that JVM died (because of Ctrl+C or SUGHUP or similar
> that happened outside of the Java code)
> or exited (because of a java.lang.System.exit() call).
This is unix environment and I suppose if we execute startup.sh tomcat runs
in background.
>
> (Well, a JVM can be configured to terminate itself on OutOfMemory
> condition, but such option (an -XX one) will be clearly visible among
> arguments of the java process).
>
> 2. 6.0.16 is so old, and I remember some fixes to shutdown process of
> Tomcat 2-3 years ago.
>
> Best regards,
> Konstantin Kolinko
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: Tomcat getting stopped when idle
Posted by Konstantin Kolinko <kn...@gmail.com>.
2013/11/1 Vidyadhar <te...@gmail.com>:
> On 1 Nov 2013 00:52, "Konstantin Kolinko" <kn...@gmail.com> wrote:
>>
>> 2013/10/31 Vidyadhar <te...@gmail.com>:
>> > Hi,
>> >
>> > We are facing some weird issue in our Tomcat environment. After starting
>> > the Tomcat process on one of our Solaris server, process is
> automatically
>> > getting shutdown after 2-3 minutes if no activity is done through
>> > Application deployed in Tomcat.
>> >
>> > I have observed similar issue in one of following mailing thread where
> as
>> > user has asked to install a Listener and print a stacktrace when the
> stop
>> > event
>> > happens. I need to know how to install such Listener.
>> >
>>
>> http://tomcat.apache.org/tomcat-6.0-doc/config/listeners.html
>>
>> There are several listeners that have been already configured there. You
> can
>> use their source code as an example.
>>
>> > http://www.mail-archive.com/users@tomcat.apache.org/msg84717.html
>> >
>> > Server version: Apache Tomcat/6.0.16
>> > Server built: Jan 28 2008 11:35:29
>> > Server number: 6.0.16.0
>> > OS Name: SunOS
>> > OS Version: 5.10
>> > Architecture: sparc
>> > JVM Version: 1.6.0_51-b11
>> > JVM Vendor: Sun Microsystems Inc.
>>
>> A recent commercial JRE, but 5,5 years old Tomcat? You may need to read
> this:
>> http://tomcat.apache.org/security-6.html
>>
>> >
>> >
>> > Error in the catalina.out
>> >
>> > Oct 30, 2013 5:04:56 AM org.apache.coyote.http11.Http11Protocol pause
>> > INFO: Pausing Coyote HTTP/1.1 on http-9920
>> > Oct 30, 2013 5:04:56 AM org.apache.catalina.connector.Connector pause
>> > SEVERE: Protocol handler pause failed
>> > java.net.ConnectException: Connection refused
>> > at java.net.PlainSocketImpl.socketConnect(Native Method)
>> > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:382)
>> > at
>> > java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:241)
>> > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:228)
>> > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:365)
>> > at java.net.Socket.connect(Socket.java:527)
>> > at java.net.Socket.connect(Socket.java:476)
>> > at java.net.Socket.<init>(Socket.java:373)
>> > at java.net.Socket.<init>(Socket.java:216)
>> > at
>> > org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:486)
>> > at
> org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:283)
>> > at org.apache.jk.server.JkMain.pause(JkMain.java:681)
>> > at
>> > org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153)
>> > at
>> > org.apache.catalina.connector.Connector.pause(Connector.java:1073)
>> > at
>> > org.apache.catalina.core.StandardService.stop(StandardService.java:563)
>> > at
>> > org.apache.catalina.core.StandardServer.stop(StandardServer.java:744)
>> > at org.apache.catalina.startup.Catalina.stop(Catalina.java:628)
>> > at
>> >
> org.apache.catalina.startup.Catalina$CatalinaShutdownHook.run(Catalina.java:671)
>>
>> Here you already have the stacktrace.
>>
>> It starts with "CatalinaShutdownHook". It means that JVM was shut down
>> by some external force (e.g. a HUP signal). Thus the shutdown hook was
>> triggered.
>>
>> Best regards,
>> Konstantin Kolinko
>>
>> ---------------------------------------------------------------------
> Hi Konstantin,
>
> To find out the actual reason we are changing log level to trace. Will keep
> you all updated on the same.
What log level?
Tuning anything on the java side is unlikely to help.
1. If shutdown is initiated by ShutdownHook like in the stacktrace
above, it means that JVM died (because of Ctrl+C or SUGHUP or similar
that happened outside of the Java code)
or exited (because of a java.lang.System.exit() call).
(Well, a JVM can be configured to terminate itself on OutOfMemory
condition, but such option (an -XX one) will be clearly visible among
arguments of the java process).
2. 6.0.16 is so old, and I remember some fixes to shutdown process of
Tomcat 2-3 years ago.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org