-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pradeep,
On 5/23/14, 2:26 PM, pradeepgm wrote:
You have a blocking AJP connector (BIO) with maxThreads of 250.
Therefore that connector can support a maximum of 250
connections. You have httpd with MaxClients 1536 and - since AJP
uses
On 23/05/2014 03:42, pradeepgm wrote:
Now we have configured three tomcat instances with below configurations to
test the above issue
1. AJP BIO with JkOptions +DisableReuse, connectionTimeout=2,
maxThreads=250, maxConnection=245
2. AJP NIO with maxThreads=250, maxConnection=245,
Attached all files here. Just masked the customer domain. conf-files.zip
http://tomcat.10.x6.nabble.com/file/n5017851/conf-files.zip
Please note that we have multiple tomcat instances supported by one common
apache httpd server. I just added the one (Tomcat 7) which is having this
issue
On 5/23/2014 8:09 AM, pradeepgm wrote:
Attached all files here. Just masked the customer domain.
conf-files.zip
http://tomcat.10.x6.nabble.com/file/n5017851/conf-files.zip
Please note that we have multiple tomcat instances supported by one
common apache httpd server. I just added the one
On 23/05/2014 17:59, Mark Eggers wrote:
In general, it's not a good idea to reference a zip file. Post
information inline without comments, and with sensitive information
obscured (not removed - since that can alter the configuration meaning).
+1
Thanks for doing this.
snip/
Connector
You have a blocking AJP connector (BIO) with maxThreads of 250.
Therefore that connector can support a maximum of 250 connections. You
have httpd with MaxClients 1536 and - since AJP uses persistent
connections - you have httpd trying to create up to 1536 persistent
connections. The first 250
On 23/05/2014 19:26, pradeepgm wrote:
You have a blocking AJP connector (BIO) with maxThreads of 250.
Therefore that connector can support a maximum of 250 connections. You
have httpd with MaxClients 1536 and - since AJP uses persistent
connections - you have httpd trying to create up to 1536
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ravi,
On 5/21/14, 2:28 AM, ravishankar_d wrote:
Hi Dan,
We are using apache web server provided along with RHEL.So I
believe we are getting back port fixes. In the threaddump we are
seeing the below long running threads many times.As
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Pradeep,
On 5/21/14, 5:15 PM, Pradeep Kumar G M wrote:
We are using mod_jk
AJP connections will always be waiting for data when they are not
actively processing a request. You should expect to see all your
idle threads sitting in this state.
Yes, we have 300 such threads waiting and after some period of time the
server is hung and not responding.
We are using AJP BIO with below parameters
maxThreads=250
maxConnection=245
--
View this message in context:
Now we have configured three tomcat instances with below configurations to
test the above issue
1. AJP BIO with JkOptions +DisableReuse, connectionTimeout=2,
maxThreads=250, maxConnection=245
2. AJP NIO with maxThreads=250, maxConnection=245, connectionTimeout=2
and bufferSize=4096
3.
Hi Dan,
We are using apache web server provided along with RHEL.So I believe we are
getting back port fixes.
In the threaddump we are seeing the below long running threads many times.As
mentioned, we are using AJP(with BIO) and tomacat 7.0.52. I wanted to know
if this will cause any issues like
On May 21, 2014, at 2:28 AM, ravishankar_d ravishanka...@infosys.com wrote:
Hi Dan,
We are using apache web server provided along with RHEL.So I believe we are
getting back port fixes.
In the threaddump we are seeing the below long running threads many times.
At a quick glance it doesn’t
At a quick glance it doesn’t seem like it would be problematic, just
reading data.
The issue is there are 300 such threads waiting
One way to test this is to disable the pooling (i.e. disablereuse=Off or
JkOptions +DisableReuse). If you disable it and you don’t see any more of
these
On May 21, 2014, at 4:03 PM, pradeepgm pradeep...@infosys.com wrote:
At a quick glance it doesn’t seem like it would be problematic, just
reading data.
The issue is there are 300 such threads waiting
One way to test this is to disable the pooling (i.e. disablereuse=Off or
We are using mod_jk
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message.
On 20/05/2014 08:01, ravishankar_d wrote:
Hi,
we are using Apache Tomcat Version 7.0.52 to deploy our Java based
application.
We have apache web server fronting the Tomcat server.We wanted to know if
there is any issue in using AJP protocol (with BIO).Apache web server
version we are using
:21 PM
To: Ravi Shankar Durga Krishna Murthy
Subject: Re: AJP protocol with Apache Tomcat Version 7.0.52
On 20/05/2014 08:01, ravishankar_d wrote:
Hi,
we are using Apache Tomcat Version 7.0.52 to deploy our Java based
application.
We have apache web server fronting the Tomcat server.We wanted
Thanks Mark.
So usage of AJP with BIO for Tomcat Version 7.0.52 should be fine.
Also is there any requirement to upgrade Apache webserver from 2.2.3?
Please let us know
Regards,
Ravi Shankar D.K
--
View this message in context:
On May 20, 2014, at 5:13 AM, ravishankar_d ravishanka...@infosys.com wrote:
Thanks Mark.
So usage of AJP with BIO for Tomcat Version 7.0.52 should be fine.
Also is there any requirement to upgrade Apache webserver from 2.2.3?
Requirement? Not to just make it work, but 2.2.3 is incredibly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 5/20/14, 7:24 AM, Daniel Mikusa wrote:
On May 20, 2014, at 5:13 AM, ravishankar_d
ravishanka...@infosys.com wrote:
Thanks Mark.
So usage of AJP with BIO for Tomcat Version 7.0.52 should be
fine. Also is there any requirement to
21 matches
Mail list logo
