You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by PJ Delsh <pj...@hotmail.com> on 2011/07/08 22:27:18 UTC
Tomcat 6.0.32 stops responding
I have an in-house designed and built SaaS application
that is running on Tomcat and Apache:
Windows Server 2003 SP2
Oracle 11g R2
Java 6 Update 26
Tomcat 6.0.32
Apache HTTPD 2.2.19
-
mod_proxy
-
mod_deflate
-
mod_ssl
For the last several weeks Tomcat stops responding during
the day, sometimes more than once.
The Tomcat
service is still running, but Tomcat is not responding to requests.
Apache & Tomcat services have to be
restarted for the app to start working again.
My guys can’t find anything in the logs that point to the
issue. We desperately need help.
Re: Tomcat 6.0.32 stops responding
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/7/11 PJ Delsh <pj...@hotmail.com>:
> 2- I don't know where in the Tomcat logs or Apache config to look for the connector we are using.
In Tomcat logs when Tomcat is starting up and is opening ports.
For AJP connector and Tomcat 6 the following lines mean that it is
using Java (Bio) implementation of AJP connector:
11.07.2011 19:55:59 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
and the following if APR implementation is used:
11.07.2011 23:26:13 org.apache.coyote.ajp.AjpAprProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-8009
The difference is in the class name on the first line of the message.
> 5- I would like to eventually setup more than one Tomcat to act as a failover.
It is documented. Also search archives of this mailing lists - people
sometimes post examples of their configuration.
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 6.0.32 stops responding
Posted by Pid <pi...@pidster.com>.
On 11/07/2011 15:10, PJ Delsh wrote:
>
> Konstantin,
> 1- We couldn't find anything useful in the Apache logs.
Log data is useful. Even if it doesn't /appear/ to show an error.
> 2- I don't know where in the Tomcat logs or Apache config to look for the connector we are using.
Carefully remove the XML comments from your Tomcat conf/server.xml and
post the result into an email here, (after testing that it still works).
> 3- How can we connect to Tomcat via the non AJP (if we are using it) to see if Tomcat responds?
By enabling and/or using the HTTP connector, usually on port 8080.
> 4- What can I do with the thread dumps?
Post them here.
> 5- I would like to eventually setup more than one Tomcat to act as a failover.
Woah, there! One problem at a time please...
p
> -PJ
>
>> Date: Mon, 11 Jul 2011 16:35:55 +0400
>> Subject: Re: Tomcat 6.0.32 stops responding
>> From: knst.kolinko@gmail.com
>> To: users@tomcat.apache.org
>>
>> 2011/7/11 PJ Delsh <pj...@hotmail.com>:
>>>
>>> Thank you Konstantin and Chris.
>>>
>>> I have setup Apache 2.2.19 through mod_jk 1.2.21
>>> To enable compression on the SSL traffic, Apache and Tomcat are setup in a reverse proxy.
>>>
>>> 1- Should I take the thread dumps now, or when Tomcat is in the 'non-responding' state?
>>
>> When it is in non-responding state.
>> Is there anything in the Apache HTTPD logs as well?
>>
>>
>> Regarding your configuration:
>> - What connector implementation you are using? (That will be in the
>> logs when Tomcat starts). Do you use Tomcat-Native aka APR
>> (bin/tcnative-1.dll) ?
>>
>> - If you have an HTTP connector besides AJP one, does Tomcat responds
>> if you try to connect to it?
>>
>>
>>> 2- Is it a good idea to make the jump from 6.0.32 to 7.0.16? I know our app works in 7.
>>
>> That is up to you to decide. The more people use Tomcat 7, the merrier it is.
>>
>>
>> Tomcat 7 releases come more frequently (once a month), and changes
>> between releases tend to be more risky, but it has better testsuite
>> than Tomcat 6.
>>
>>
>> There was some connector refactoring recently in Tomcat 7, to reduce
>> duplicate code and simplify further development and maintenance. Next
>> release will be 7.0.19.
>>
>> Regarding your issue, I do not think that the upgrade will change
>> anything in diagnosing the issue.
>>
>>
>> There should be other reasons for upgrading, like parallel deployment,
>> or using Sevlet 3.0 features in applications that you will deploy on
>> the same server later.
>>
>> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment
>>
>>
>>> 3- If I was to hire a consultant to look into this, can you recommend one?
>>
>> http://wiki.apache.org/tomcat/SupportAndTraining
>>
>> 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 6.0.32 stops responding
Posted by PJ Delsh <pj...@hotmail.com>.
Konstantin,
1- We couldn't find anything useful in the Apache logs.
2- I don't know where in the Tomcat logs or Apache config to look for the connector we are using.
3- How can we connect to Tomcat via the non AJP (if we are using it) to see if Tomcat responds?
4- What can I do with the thread dumps?
5- I would like to eventually setup more than one Tomcat to act as a failover.
-PJ
> Date: Mon, 11 Jul 2011 16:35:55 +0400
> Subject: Re: Tomcat 6.0.32 stops responding
> From: knst.kolinko@gmail.com
> To: users@tomcat.apache.org
>
> 2011/7/11 PJ Delsh <pj...@hotmail.com>:
> >
> > Thank you Konstantin and Chris.
> >
> > I have setup Apache 2.2.19 through mod_jk 1.2.21
> > To enable compression on the SSL traffic, Apache and Tomcat are setup in a reverse proxy.
> >
> > 1- Should I take the thread dumps now, or when Tomcat is in the 'non-responding' state?
>
> When it is in non-responding state.
> Is there anything in the Apache HTTPD logs as well?
>
>
> Regarding your configuration:
> - What connector implementation you are using? (That will be in the
> logs when Tomcat starts). Do you use Tomcat-Native aka APR
> (bin/tcnative-1.dll) ?
>
> - If you have an HTTP connector besides AJP one, does Tomcat responds
> if you try to connect to it?
>
>
> > 2- Is it a good idea to make the jump from 6.0.32 to 7.0.16? I know our app works in 7.
>
> That is up to you to decide. The more people use Tomcat 7, the merrier it is.
>
>
> Tomcat 7 releases come more frequently (once a month), and changes
> between releases tend to be more risky, but it has better testsuite
> than Tomcat 6.
>
>
> There was some connector refactoring recently in Tomcat 7, to reduce
> duplicate code and simplify further development and maintenance. Next
> release will be 7.0.19.
>
> Regarding your issue, I do not think that the upgrade will change
> anything in diagnosing the issue.
>
>
> There should be other reasons for upgrading, like parallel deployment,
> or using Sevlet 3.0 features in applications that you will deploy on
> the same server later.
>
> http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment
>
>
> > 3- If I was to hire a consultant to look into this, can you recommend one?
>
> http://wiki.apache.org/tomcat/SupportAndTraining
>
> 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 6.0.32 stops responding
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/7/11 PJ Delsh <pj...@hotmail.com>:
>
> Thank you Konstantin and Chris.
>
> I have setup Apache 2.2.19 through mod_jk 1.2.21
> To enable compression on the SSL traffic, Apache and Tomcat are setup in a reverse proxy.
>
> 1- Should I take the thread dumps now, or when Tomcat is in the 'non-responding' state?
When it is in non-responding state.
Is there anything in the Apache HTTPD logs as well?
Regarding your configuration:
- What connector implementation you are using? (That will be in the
logs when Tomcat starts). Do you use Tomcat-Native aka APR
(bin/tcnative-1.dll) ?
- If you have an HTTP connector besides AJP one, does Tomcat responds
if you try to connect to it?
> 2- Is it a good idea to make the jump from 6.0.32 to 7.0.16? I know our app works in 7.
That is up to you to decide. The more people use Tomcat 7, the merrier it is.
Tomcat 7 releases come more frequently (once a month), and changes
between releases tend to be more risky, but it has better testsuite
than Tomcat 6.
There was some connector refactoring recently in Tomcat 7, to reduce
duplicate code and simplify further development and maintenance. Next
release will be 7.0.19.
Regarding your issue, I do not think that the upgrade will change
anything in diagnosing the issue.
There should be other reasons for upgrading, like parallel deployment,
or using Sevlet 3.0 features in applications that you will deploy on
the same server later.
http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment
> 3- If I was to hire a consultant to look into this, can you recommend one?
http://wiki.apache.org/tomcat/SupportAndTraining
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 6.0.32 stops responding
Posted by PJ Delsh <pj...@hotmail.com>.
Thank you Konstantin and Chris.
I have setup Apache 2.2.19 through mod_jk 1.2.21
To enable compression on the SSL traffic, Apache and Tomcat are setup in a reverse proxy.
1- Should I take the thread dumps now, or when Tomcat is in the 'non-responding' state?
2- Is it a good idea to make the jump from 6.0.32 to 7.0.16? I know our app works in 7.
3- If I was to hire a consultant to look into this, can you recommend one? pjdelsh007@hotmail
> Date: Sun, 10 Jul 2011 10:36:01 -0400
> From: chris@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: Tomcat 6.0.32 stops responding
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Konstantin,
>
> On 7/8/2011 5:00 PM, Konstantin Kolinko wrote:
> > You have to take three thread dumps with small interval between
> > them, to see what Tomcat is actually doing. (How to make dumps ->
> > see FAQ).
>
> +1
>
> > One usual cause is when you have infinite timeout on you database
> > connection pool. So threads are waiting for your DB. (If you are
> > not recycling sql objects properly, you may run out of them easily).
>
> PJ, there have been some recent problems discovered in the NIO connector
> that cause request processing threads to be lost from the pool, but I
> believe all of those were fixed by 6.0.32.
>
> If you post back, please include your <Connector> configuration and tell
> us which connector you are intending to use (unless specifically
> configured, you can't tell the difference between an AJP and non-AJP
> connector, for instance).
>
> Thanks,
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk4ZuNEACgkQ9CaO5/Lv0PD5MwCgv9wG6OfjGZZwPGTyY1qP4935
> /8oAn2Ramqqk59K9HnY6a/q8SUtZ3MYn
> =7jmv
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: Tomcat 6.0.32 stops responding
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Konstantin,
On 7/8/2011 5:00 PM, Konstantin Kolinko wrote:
> You have to take three thread dumps with small interval between
> them, to see what Tomcat is actually doing. (How to make dumps ->
> see FAQ).
+1
> One usual cause is when you have infinite timeout on you database
> connection pool. So threads are waiting for your DB. (If you are
> not recycling sql objects properly, you may run out of them easily).
PJ, there have been some recent problems discovered in the NIO connector
that cause request processing threads to be lost from the pool, but I
believe all of those were fixed by 6.0.32.
If you post back, please include your <Connector> configuration and tell
us which connector you are intending to use (unless specifically
configured, you can't tell the difference between an AJP and non-AJP
connector, for instance).
Thanks,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk4ZuNEACgkQ9CaO5/Lv0PD5MwCgv9wG6OfjGZZwPGTyY1qP4935
/8oAn2Ramqqk59K9HnY6a/q8SUtZ3MYn
=7jmv
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 6.0.32 stops responding
Posted by Konstantin Kolinko <kn...@gmail.com>.
2011/7/9 PJ Delsh <pj...@hotmail.com>:
>
> For the last several weeks Tomcat stops responding during
> the day, sometimes more than once.
> The Tomcat
> service is still running, but Tomcat is not responding to requests.
> Apache & Tomcat services have to be
> restarted for the app to start working again.
>
> My guys can’t find anything in the logs that point to the
> issue. We desperately need help.
See previous such questions in the archives.
You have to take three thread dumps with small interval between them,
to see what Tomcat is actually doing. (How to make dumps -> see FAQ).
One usual cause is when you have infinite timeout on you database
connection pool. So threads are waiting for your DB. (If you are not
recycling sql objects properly, you may run out of them easily).
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org