Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BAY148-w46369EEEDE66CA9FAF416394420@phx.gbl>
References: <BAY148-w3721FAA7DC994D6A023F4D94400@phx.gbl>
	<CABzHfV=r3EfCvMs8dhwnV2QwDLFfarxsPWK=tbHH_aC=j-FMKA@mail.gmail.com>
	<4E19B8D1.9050908@christopherschultz.net>
	<BAY148-w46369EEEDE66CA9FAF416394420@phx.gbl>
Date: Mon, 11 Jul 2011 16:35:55 +0400
Message-ID: 
 <CABzHfVkxAd-eH0z7jspK8Qrx4M-H7kXhT4m-XviuXgqC_x3YvA@mail.gmail.com>
Subject: Re: Tomcat 6.0.32 stops responding
From: Konstantin Kolinko <knst.kolinko@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2011/7/11 PJ Delsh <pjdelsh007@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-resp=
onding' 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? =A0I know ou=
r app works in 7.

That is up to you to decide. The more people use Tomcat 7, the merrier it i=
s.


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_deploy=
ment


> 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