/2 things get more complex.
For example, the socket timeout for async is infinite and Tomcat manages
the async timeout separately.
The docs could do with an update.
Mark
On 04/11/2022 11:45, Pawel Veselov wrote:
Hello.
I was wondering what exact value does Tomcat 9x use for NIO connector
Hello.
I was wondering what exact value does Tomcat 9x use for NIO connector
socket timeouts?
I.e., when the following exception occurs:
org.apache.catalina.connector.ClientAbortException
java.net.SocketTimeoutException
at
org.apache.catalina.connector.OutputBuffer.realWriteBytes
:
https://tomcat.apache.org/migration-9.html#BIO_connector_removed)
May I know the major difference on BIO connector and NIO connector ?
https://tomcat.apache.org/tomcat-8.0-doc/config/http.html#Connector_Comparison
Note also that the APR/native Connector has been deprecated and removed
in Tomcat
#BIO_connector_removed)
May I know the major difference on BIO connector and NIO connector ?
https://tomcat.apache.org/tomcat-8.0-doc/config/http.html#Connector_Comparison
Note also that the APR/native Connector has been deprecated and removed
in Tomcat 10.1.x onwards.
if NIO have better performance, where
connector and NIO connector ? if NIO
have better performance, where can I get the bench mark comparison report ?
Regards,
Terry
t is in charge of Tomcat. I would like to understand all
> the steps a request goes through in order to be handled and alsohow
> does the NIO connector works considering mainly those three
> parameters: - maxConnections - acceptCount - maxThreads
There's a lot of information to giv
which way the
application is handling incoming connections from the clients.
Is there any resource that explains what is in charge of the operating
system and what is in charge of Tomcat. I would like to understand all the
steps a request goes through in order to be handled and alsohow does the
NIO
On Thu, Dec 20, 2018 at 9:37 PM John Palmer wrote:
> I'm working with tomcat 8.5.35 to configure SSL
> (current system is tomcat 7.5 using JKS keystore and truststore)..
>
> I finally have the certificate parts working with the default (commented
> out) APR connector..
> it bothers me (doesn'
I'm working with tomcat 8.5.35 to configure SSL
(current system is tomcat 7.5 using JKS keystore and truststore)..
I finally have the certificate parts working with the default (commented
out) APR connector..
it bothers me (doesn't seem intuitive) that the logging shows
"useAprConnector [false
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Saurav,
On 10/11/17 8:56 AM, Saurav Sarkar wrote:
> I have got a basic question related to usage of Async servlet with
> tomcat NIO connector.
>
> I want to use Async servlet with Non Block I/O as per servlet spec
> https://docs.or
Hi All,
I have got a basic question related to usage of Async servlet with tomcat
NIO connector.
I want to use Async servlet with Non Block I/O as per servlet spec
https://docs.oracle.com/javaee/7/tutorial/servlets013.htm?lipi=urn%3Ali%3Apage%3Ad_flagship3_pulse_read%3BmL0Q5Y7ESTy4lpYPU%2Br77w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Swati,
On 8/11/16 2:16 AM, swati jain wrote:
> Tomcat Version - 8.5.4 ( Embedded) Platform - Linux
>
> When NIO connector is used with Embedded Tomcat, it creates a
> session per request. The session lasts for 30 minutes. Is ther
Tomcat Version - 8.5.4 ( Embedded)
Platform - Linux
When NIO connector is used with Embedded Tomcat, it creates a session per
request. The session lasts for 30 minutes. Is there a way to configure
connector in such a way that no session is created. I have traffic of around
4 requests per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor,
On 5/24/16 6:52 PM, Igor Cicimov wrote:
> On 24 May 2016 12:33 pm, "Christopher Schultz"
> wrote:
>>
> Jakub,
>
> On 5/23/16 8:03 PM, Ja kub wrote:
Christopher, Thx for response, pleas confirm or deny if I
understand well.
>>
On 24 May 2016 12:33 pm, "Christopher Schultz"
wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakub,
>
> On 5/23/16 8:03 PM, Ja kub wrote:
> > Christopher, Thx for response, pleas confirm or deny if I
> > understand well.
> >
> > BIO uses thread per http connection (tcp connectio
Christopher, Great Thanks.
BR
Jakub
On Tue, May 24, 2016 at 4:33 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakub,
>
> On 5/23/16 8:03 PM, Ja kub wrote:
> > Christopher, Thx for response, pleas confirm or deny if I
> > un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jakub,
On 5/23/16 8:03 PM, Ja kub wrote:
> Christopher, Thx for response, pleas confirm or deny if I
> understand well.
>
> BIO uses thread per http connection (tcp connection). (Shame I
> didn't realize it!) NIO uses thread per request.
It's more
schultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Jakub,
>
> On 5/23/16 11:38 AM, Ja kub wrote:
> > In which scenario nio connector will outerform basic io connector
> > and vice versa ?
>
> In Tomcat 8.5 and higher, NIO will always outperfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jakub,
On 5/23/16 11:38 AM, Ja kub wrote:
> In which scenario nio connector will outerform basic io connector
> and vice versa ?
In Tomcat 8.5 and higher, NIO will always outperform the BIO connector
because the BIO connector has been comp
Hello,
In which scenario nio connector will outerform basic io connector and vice
versa ?
What would be high level design of corresponding performance tests showing
advantages of each connector ?
BR
Jakub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
João,
On 1/28/16 3:09 PM, João Sávio wrote:
> I'm using Tomcat 7.0.53 and I've changed it to use the NIO
> connector recently. So, the following error start appearing on the
> logs (few per day)
>
>
Hello guys
I'm using Tomcat 7.0.53 and I've changed it to use the NIO connector
recently. So, the following error start appearing on the logs (few per day)
Jan 25, 2016 3:10:16 PM org.apache.tomcat.util.net.NioEndpoint processSocket
SEVERE: Error allocating socket
On 23/03/2014 12:41, Martin Gainty wrote:
>
>> Date: Sat, 22 Mar 2014 14:24:01 -0400
>> Subject: Effects of turning off sendFile in the NIO connector
>> From: tomcat.ran...@gmail.com
>> To: users@tomcat.apache.org
>>
>> What effect would setting useSendfil
>
> John
>
> The consequences for disabling sendFile are extremely hard to quantify
> as there are so many variables. I would normally expect there to be more
> CPU load but how much more? No idea. It might be impossible to detect,
> it might leaver your CPUs pegged at 100%.
>
> The only way you wi
On 23/03/2014 19:37, John Smith wrote:
>>> We also only really need compression on XML data, the site has minimal
>>> HTML, SWF's don't really benefit from gzip and some binary data we send
>>> back and forth is already compressed. I could manually implement
>>> compression on XML at the applicati
.0.42
> > RHEL6
> > ~4T outbound traffic/day
> >
> > Best,
> > John
>
>
Your first link refers to using sendFile for asynchronous writes from a
servlet. "Any servlet can instruct Tomcat to perform a sendfile call by
setting the appropriate request attributes.&qu
> Date: Sat, 22 Mar 2014 14:24:01 -0400
> Subject: Effects of turning off sendFile in the NIO connector
> From: tomcat.ran...@gmail.com
> To: users@tomcat.apache.org
>
> What effect would setting useSendfile=false have on a web application using
> the NIO connector?
What effect would setting useSendfile=false have on a web application using
the NIO connector? I'm asking because I may want to use gzip compression in
the connector. The docs state:
*"There is a tradeoff between using compression (saving your bandwidth) and
using the sendfile featu
>
>
> Collecting some peak usage data might be interesting. You definitely want
> your max thread limit to be a bit above the number of concurrent requests
> you're handling. Of course, that has to be balanced against limits on
> other resources, such as memory and data base connections.
>
> - C
> From: John Smith [mailto:tomcat.ran...@gmail.com]
> Subject: Re: NIO connector - connections and threads
> If you're implying are 200 people simultaneously, hitting the same page at
> the same time, or making the same HTTP POST at the same time, the answer
> is, yes, probab
On Mon, Mar 10, 2014 at 11:48 AM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: John Smith [mailto:tomcat.ran...@gmail.com]
> > Subject: Re: NIO connector - connections and threads
>
> Don't top post.
>
> > So are the open HTTP connec
> From: John Smith [mailto:tomcat.ran...@gmail.com]
> Subject: Re: NIO connector - connections and threads
Don't top post.
> So are the open HTTP connections that use my web application code waiting
> in line to be processed by the available threads specified in maxThreads?
gt; Sorry, forgot: Tomcat 7.0.42
> >
> >
> > On Fri, Mar 7, 2014 at 3:59 PM, John Smith
> wrote:
> >
> >> The NIO connector has two attributes from the standard HTTP Connector
> >> implementation, maxConnections and maxThreads with defaults of 1 and
&
2014-03-09 2:08 GMT+04:00 John Smith :
> Sorry, forgot: Tomcat 7.0.42
>
>
> On Fri, Mar 7, 2014 at 3:59 PM, John Smith wrote:
>
>> The NIO connector has two attributes from the standard HTTP Connector
>> implementation, maxConnections and maxThreads with defaults of 100
Sorry, forgot: Tomcat 7.0.42
On Fri, Mar 7, 2014 at 3:59 PM, John Smith wrote:
> The NIO connector has two attributes from the standard HTTP Connector
> implementation, maxConnections and maxThreads with defaults of 1 and
> 200, respectively.
>
> Can anyone shine some lig
The NIO connector has two attributes from the standard HTTP Connector
implementation, maxConnections and maxThreads with defaults of 1 and
200, respectively.
Can anyone shine some light on how these work together? If I'm allowing up
to 1 connections, would that mean I only hav
On 11/7/2013 12:51 PM, Mark Thomas wrote:
> On 07/11/2013 18:20, Bob DeRemer wrote:
>> Guys,
>>
>> I wanted to follow back around on some of the websocket load testing
>> we’ve been doing in EC2.The good news is, we were able to get 100K
>> websockets connected directly to a single Tomcat insta
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Thursday, November 07, 2013 1:52 PM
> To: Tomcat Users List
> Subject: Re: (working) high load (100K+) websocket + NIO connector setting
> comparison on 1 Tomcat 7 instance
>
> On 07/11
On 07/11/2013 18:20, Bob DeRemer wrote:
> Guys,
>
> I wanted to follow back around on some of the websocket load testing
> we’ve been doing in EC2.The good news is, we were able to get 100K
> websockets connected directly to a single Tomcat instance (EASILY)
Excellent.
> My theory is it’s a
Guys,
I wanted to follow back around on some of the websocket load testing we've been
doing in EC2.The good news is, we were able to get 100K websockets
connected directly to a single Tomcat instance (EASILY) - once we got the
settings right. As a result, I wanted to post my results here f
Hi All,
>>>>
>>>> We are currently using HTTP connector in tomcat 7.42 and
>>>> planning to switch to AJP NIO connector. When I was reading
>>>> through the docs I found "WARNING: The NIO connector for AJP
>>>> is experimental."
On 06/08/2013 16:09, Christopher Schultz wrote:
> Mark,
>
> On 8/5/13 10:12 AM, Mark Thomas wrote:
>> On 05/08/2013 15:50, Abhijith Prabhakar wrote:
>>> Hi All,
>>>
>>> We are currently using HTTP connector in tomcat 7.42 and planning
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 8/5/13 10:12 AM, Mark Thomas wrote:
> On 05/08/2013 15:50, Abhijith Prabhakar wrote:
>> Hi All,
>>
>> We are currently using HTTP connector in tomcat 7.42 and planning
>> to switch to AJP NIO connector. Whe
currently using HTTP connector in tomcat 7.42 and planning to
>> switch to AJP NIO connector. When I was reading through the docs I
>> found "WARNING: The NIO connector for AJP is experimental."
>>
>> This made me think that NIO connector might not be mature at t
On 05/08/2013 15:50, Abhijith Prabhakar wrote:
> Hi All,
>
> We are currently using HTTP connector in tomcat 7.42 and planning to
> switch to AJP NIO connector. When I was reading through the docs I
> found "WARNING: The NIO connector for AJP is experimental."
>
&
Hi All,
We are currently using HTTP connector in tomcat 7.42 and planning to switch to
AJP NIO connector. When I was reading through the docs I found "WARNING: The
NIO connector for AJP is experimental."
This made me think that NIO connector might not be mature at this point. Can
Hi,
Not sure if anyone has used NIO connector in embedded tomcat 7 but I am
out of luck so far. It seems so simple but I could not get it work. I am
wondering if this is a bug in embedded version of tomcat because it works
fine on standalone version. If this turns out to be a bug in tomcat 7
Sorry I meant "nio" connector not bio connector. Outlook auto-correct is
not smart enough :)
On 4/23/13 Apr 23, 12:08 PM, "Praveen Peddi"
wrote:
>I am not sure if this is the same issue I am having but apparently I am
>also using atmosphere for web sockets and make
/apache/catalina/start
up/TomcatBaseTest.java
Thanks
Praveen
On 4/23/13 Apr 23, 10:40 AM, "Tribon Cheng" wrote:
>Just like this issue:
>
>http://atmosphere-framework.2306103.n4.nabble.com/WebSocket-not-working-on
>-Tomcat-7-With-NIO-connector-was-WebSocket-not-working-on-Tomc
Just like this issue:
http://atmosphere-framework.2306103.n4.nabble.com/WebSocket-not-working-on-Tomcat-7-With-NIO-connector-was-WebSocket-not-working-on-Tomcat-7-td4652351.html
On Tue, Apr 23, 2013 at 10:16 PM, Mark Thomas wrote:
> On 23/04/2013 15:11, Praveen Peddi wrote:
> > Hi
On 23/04/2013 15:11, Praveen Peddi wrote:
> Hi all, I am trying to set Nio connector in tomcat7 so I can use
> WebSocket support. I did the following (as simple as it can get) but
> it doesn't seem to work. When I do this I can't connect to the
> server. For example I have a
Hi all,
I am trying to set Nio connector in tomcat7 so I can use WebSocket support. I
did the following (as simple as it can get) but it doesn't seem to work. When I
do this I can't connect to the server. For example I have a GET REST request
that should work but I get connection ref
ike we can grep
> the Tomcat code for "new UNIXDomainSocket" or anything like that.
>
>> The leak is absent when Tomcat runs using the BIO connector, and
>> this would indicate a problem in the NIO connector implementation.
>>
>> I've seen the same situation i
like we can grep
the Tomcat code for "new UNIXDomainSocket" or anything like that.
> The leak is absent when Tomcat runs using the BIO connector, and
> this would indicate a problem in the NIO connector implementation.
>
> I've seen the same situation indicated by
to:icici...@gmail.com]
> Sent: Tuesday, January 15, 2013 5:19 PM
> To: Tomcat Users List
> Subject: Re: NIO connector issue: SEVERE: Error processing request
>
> On Wed, Jan 16, 2013 at 9:34 AM, Kevin Priebe >wrote:
>
> > Hi,
> >
> >
> >
> > We have a
and will gather a
bunch of more info as Igor and Chris suggested.
Kevin
-Original Message-
From: Igor Cicimov [mailto:icici...@gmail.com]
Sent: Tuesday, January 15, 2013 5:19 PM
To: Tomcat Users List
Subject: Re: NIO connector issue: SEVERE: Error processing request
On Wed, Jan 16,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Kevin,
On 1/15/13 5:34 PM, Kevin Priebe wrote:
> We have a setup with Nginx load balancing between 2 clustered
> tomcat instances. 1 instance is on the same server as Nginx and
> the other is on a separate physical server (same rackspace). We’re
>
27;t hurt to
ask), switch problems etc? What else is between nginx and tomcat 2? Can you
see in the nginx logs how much time the requests to instance 1 and instance
2 take? Also by comparing timestamps you should be able to find in nginx
the request that failed (there must be error on nginx side too) and
Hi,
We have a setup with Nginx load balancing between 2 clustered tomcat instances.
1 instance is on the same server as Nginx and the other is on a separate
physical server (same rackspace). We’re using pretty standard default settings
and are using the NIO tomcat connector. Tomcat versio
usa [mailto:dmik...@vmware.com]
> > Sent: Wednesday, September 12, 2012 2:14 PM
> > To: Tomcat Users List
> > Subject: Re: HTTP NIO connector not supporting IPv6
> >
> > On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
> >
> > >> -Original Me
> -Original Message-
> From: Daniel Mikusa [mailto:dmik...@vmware.com]
> Sent: Wednesday, September 12, 2012 2:14 PM
> To: Tomcat Users List
> Subject: Re: HTTP NIO connector not supporting IPv6
>
> On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
>
&g
On Sep 12, 2012, at 2:44 PM, Jeffrey Janner wrote:
>> -Original Message-
>> From: Daniel Mikusa [mailto:dmik...@vmware.com]
>> Sent: Wednesday, September 12, 2012 10:00 AM
>> To: Tomcat Users List
>> Subject: Re: HTTP NIO connector not supporting IPv6
>
> -Original Message-
> From: Daniel Mikusa [mailto:dmik...@vmware.com]
> Sent: Wednesday, September 12, 2012 10:00 AM
> To: Tomcat Users List
> Subject: Re: HTTP NIO connector not supporting IPv6
>
> On Sep 12, 2012, at 1:29 AM, Aditi Sinha wrote:
&g
xx"/>
>
>
>
> Please let me know if something missing here?
>
>
>
> Thanks & Regards,
>
> Aditi
>
>
> On Tue, Sep 11, 2012 at 7:30 PM, Jeffrey Janner > wrote:
>
>>> -Original Message-
>>> From: Jeffrey Janner [ma
ower versions, but I don't think any
> that affect the connector mechanism.
>
>
> > > -Original Message-
> > > From: Aditi Sinha [mailto:adisinha0...@gmail.com]
> > > Sent: Tuesday, September 11, 2012 7:21 AM
> > > To: Tomcat Users List
> > &
> -Original Message-
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Sent: Tuesday, September 11, 2012 8:57 AM
> To: 'Tomcat Users List'
> Subject: RE: HTTP NIO connector not supporting IPv6
>
> Aditi -
>
> All connectors support both I
errors in your catalina.log file, those would be helpful as well.
Jeff
> -Original Message-
> From: Aditi Sinha [mailto:adisinha0...@gmail.com]
> Sent: Tuesday, September 11, 2012 7:21 AM
> To: Tomcat Users List
> Subject: HTTP NIO connector not supporting IPv6
>
>
SSL requests: Connector with
> protocol="org.apache.coyote.http11.Http11NioProtocol" (HTTP NIO
> connector)
>
>
>
> With the above configuration server is not accessible through the IPv6
> address. The “netstat –an” command also does not list the connector
&
connector)
2. For SSL requests: Connector with
protocol="org.apache.coyote.http11.Http11NioProtocol" (HTTP NIO
connector)
With the above configuration server is not accessible through the IPv6
address. The “netstat –an” command also does not list the connector
ports(d
Just a heads up to the Tomcat team - I switched all our comet handling to
Jetty, and these issues are resolved. Something is definitely amiss in the
NIO connector.
Regards,
Matt Tyson
On Sat, Dec 31, 2011 at 10:23 AM, Mark Thomas wrote:
> On 31/12/2011 16:35, Matthew Tyson wrote:
> &g
On 31/12/2011 16:35, Matthew Tyson wrote:
> On Wed, Dec 28, 2011 at 1:04 AM, wrote:
>
>> Matthew Tyson wrote:
>>
>>> That's right, there is an f5 load balancer. The valve is used to keep
>>> track of whether the request was via HTTPS or not.
>>
>> What happens if you go direct to Tomcat and byp
On Wed, Dec 28, 2011 at 1:04 AM, wrote:
> Matthew Tyson wrote:
>
> >That's right, there is an f5 load balancer. The valve is used to keep
> >track of whether the request was via HTTPS or not.
>
> What happens if you go direct to Tomcat and bypass the F5?
>
> >tcpdump seems to confirm the same.
On 29/12/2011 19:22, Matthew Tyson wrote:
> On Thu, Dec 29, 2011 at 11:07 AM, Pid wrote:
>
>> On 29/12/2011 17:27, Matthew Tyson wrote:
>>> On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson
>>> wrote:
>>>
On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr >> wrote:
> Am 28.12.2011 10:04, sch
On Thu, Dec 29, 2011 at 12:02 PM, Tim Watts wrote:
> On Thu, 2011-12-29 at 11:22 -0800, Matthew Tyson wrote:
>
>
>
> > How an empty 200 response could be generated
> > without executing the logging statement here is a mystery.
> >
>
> Do you still have that MonitoringFilter configured in the web
On Thu, 2011-12-29 at 11:22 -0800, Matthew Tyson wrote:
> How an empty 200 response could be generated
> without executing the logging statement here is a mystery.
>
Do you still have that MonitoringFilter configured in the web app?
Perhaps it is short circuiting the chain.
> protected void
On 29/12/2011 17:27, Matthew Tyson wrote:
> On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson
> wrote:
>
>> On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr wrote:
>>
>>> Am 28.12.2011 10:04, schrieb ma...@apache.org:
>>>
>>> Matthew Tyson>
wrote:
That's right, there is an f5 load balan
On Thu, Dec 29, 2011 at 11:07 AM, Pid wrote:
> On 29/12/2011 17:27, Matthew Tyson wrote:
> > On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson
> > wrote:
> >
> >> On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr >wrote:
> >>
> >>> Am 28.12.2011 10:04, schrieb ma...@apache.org:
> >>>
> >>> Matthew Tyso
On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson
wrote:
> On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr wrote:
>
>> Am 28.12.2011 10:04, schrieb ma...@apache.org:
>>
>> Matthew Tyson>
>>> wrote:
>>>
>>> That's right, there is an f5 load balancer. The valve is used to keep
track of whether th
On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr wrote:
> Am 28.12.2011 10:04, schrieb ma...@apache.org:
>
> Matthew Tyson>
>> wrote:
>>
>> That's right, there is an f5 load balancer. The valve is used to keep
>>> track of whether the request was via HTTPS or not.
>>>
>>
>> What happens if you go
Am 28.12.2011 10:04, schrieb ma...@apache.org:
Matthew Tyson wrote:
That's right, there is an f5 load balancer. The valve is used to keep
track of whether the request was via HTTPS or not.
What happens if you go direct to Tomcat and bypass the F5?
tcpdump seems to confirm the same. What
Matthew Tyson wrote:
>That's right, there is an f5 load balancer. The valve is used to keep
>track of whether the request was via HTTPS or not.
What happens if you go direct to Tomcat and bypass the F5?
>tcpdump seems to confirm the same. What are you thinking?
Probably, like me, that the F5
On Tue, Dec 27, 2011 at 1:31 PM, Stefan Mayr wrote:
> Am 24.12.2011 00:39, schrieb Matthew Tyson:
>
> Hello,
>>
>> We have been having quite a few problems with using long-polling
>> connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
>> d
Am 24.12.2011 00:39, schrieb Matthew Tyson:
Hello,
We have been having quite a few problems with using long-polling
connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
definitely improved things, but we are still seeing major issues.
The problems only crop up after a
On Tue, Dec 27, 2011 at 11:11 AM, Mark Thomas wrote:
> On 25/12/2011 02:17, Matthew Tyson wrote:
>
> >> INFO 2011-12-24 10:25:35,578 COMET REQUEST: 75.149.42.46 POST null |
> >> TRACE:
> >> java.lang.Throwable
> >> at
> org.cometd.server.CometdServlet.service(CometdServlet.java:149)
>
On 25/12/2011 02:17, Matthew Tyson wrote:
>> INFO 2011-12-24 10:25:35,578 COMET REQUEST: 75.149.42.46 POST null |
>> TRACE:
>> java.lang.Throwable
>> at org.cometd.server.CometdServlet.service(CometdServlet.java:149)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java
; We have been having quite a few problems with using long-polling
>>> > connections in Tomcat, via the NIO connector. Upgrading to Tomcat
>>> 7.0.23
>>> > definitely improved things, but we are still seeing major issues.
>>>
>>> Glad to hear things are get
On Sat, Dec 24, 2011 at 10:33 AM, Matthew Tyson
wrote:
> On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomas wrote:
>
>> On 23/12/2011 23:39, Matthew Tyson wrote:
>> > Hello,
>> >
>> > We have been having quite a few problems with using long-polling
>> &
Am 24.12.2011 19:33, schrieb Matthew Tyson:
On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomas wrote:
On 23/12/2011 23:39, Matthew Tyson wrote:
Hello,
We have been having quite a few problems with using long-polling
connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomas wrote:
> On 23/12/2011 23:39, Matthew Tyson wrote:
> > Hello,
> >
> > We have been having quite a few problems with using long-polling
> > connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
> > d
On 23/12/2011 23:39, Matthew Tyson wrote:
> Hello,
>
> We have been having quite a few problems with using long-polling
> connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
> definitely improved things, but we are still seeing major issues.
Glad to hear thi
Hello,
We have been having quite a few problems with using long-polling
connections in Tomcat, via the NIO connector. Upgrading to Tomcat 7.0.23
definitely improved things, but we are still seeing major issues.
The problems only crop up after a couple minutes under some load (modest
load
gt;> In which scenarios would we tend to use the default connector, and in
>>> which
>>> scenarios will it be more appropriate to use the NIO connector?
>>>
>> NIO and APR use one thread per currently processing request.
>> BIO uses one thread per connect
the NIO connector?
NIO and APR use one thread per currently processing request.
BIO uses one thread per connection. Since usually connections>>
currently processing request, NIO and APR scale better.
BIO has slightly better raw performance than NIO (excluding sendfile).
It used
onnector, and in
> which
> > scenarios will it be more appropriate to use the NIO connector?
>
> NIO and APR use one thread per currently processing request.
> BIO uses one thread per connection. Since usually connections >>
> currently processing request, NIO and APR scale bette
On 17/02/2011 14:56, Afkham Azeez wrote:
> Hi folks,
> What is the advantage of using this connector as opposed to the default one?
> In which scenarios would we tend to use the default connector, and in which
> scenarios will it be more appropriate to use the NIO connector?
NIO and
Hi folks,
What is the advantage of using this connector as opposed to the default one?
In which scenarios would we tend to use the default connector, and in which
scenarios will it be more appropriate to use the NIO connector?
Thanks
Azeez
*
*
Christopher,
Thanks for the help. I will log this in Bugzilla shortly.
-parag
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Saturday, February 05, 2011 4:06 AM
To: Tomcat Users List
Subject: Re: Nio Connector and self signed SSL certificate
.
Regards,
Parag
-Original Message-
From: Brett Delle Grazie [mailto:brett.dellegra...@gmail.com]
Sent: Saturday, February 05, 2011 1:30 PM
To: Tomcat Users List
Subject: Re: Nio Connector and self signed SSL certificate giving "No client
certificate chain in this request"
Hi,
On 4 February 2011 22:36, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Parag,
>
> On 2/4/2011 5:04 AM, Parag Thakur wrote:
>
>> When I try to access a secure URL (e.g. /secure/foo.do) from a java
>> program using apache httpclient library (where the client
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Parag,
On 2/4/2011 5:04 AM, Parag Thakur wrote:
> When I try to access a secure URL (e.g. /secure/foo.do) from a java
> program using apache httpclient library (where the client is configured
> to use "C:\keys\webserver.keystore" as the truststore an
1 - 100 of 207 matches
Mail list logo
