Re: Tomcat 9x NIO connector socket timeout

/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

Tomcat 9x NIO connector socket timeout

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

Re: BIO connector vs NIO connector

: 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

Re: BIO connector vs NIO connector

#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

BIO connector vs NIO connector

connector and NIO connector ? if NIO have better performance, where can I get the bench mark comparison report ? Regards, Terry

Re: Understanding NIO connector

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 give

Understanding NIO connector

in 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

Re: tomcat 8.5.35 warning using NIO 2 (or NIO) connector w APR: An unknown setting with identifier [2147483647] and value [2] was ignored

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

tomcat 8.5.35 warning using NIO 2 (or NIO) connector w APR: An unknown setting with identifier [2147483647] and value [2] was ignored

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

Re: Basic question related to NIO connector and Async servlet processing

-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

Basic question related to NIO connector and Async servlet processing

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

Re: Tomcat 8.5.4 making sessions when used with NIO connector

-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 t

Tomcat 8.5.4 making sessions when used with NIO connector

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

Re: nio connector

-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

Re: nio connector

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

Re: nio connector

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 > >

Re: nio connector

-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

Re: nio connector

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 outperform the BIO conn

Re: nio connector

-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

nio connector

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

Re: NullPointerException when using NIO connector

-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) > > Jan 25,

NullPointerException when using NIO connector

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 processor

[OT] Re: Effects of turning off sendFile in the NIO connector

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 useSendfile=false have on a web application using the NIO

RE: Effects of turning off sendFile in the NIO connector

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? I'm asking because I may want

Re: Effects of turning off sendFile in the NIO connector

by setting the appropriate request attributes. Your answer is not accurate. I don't need to do anything explicitly with the headers. You should look at the documentation regarding the HTTP NIO Connector - which you already have as the second link in your reply. It discusses sendFile and compression

Re: Effects of turning off sendFile in the NIO connector

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 application level

Re: Effects of turning off sendFile in the NIO connector

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 will know

Effects of turning off sendFile in 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 feature (saving your

Re: NIO connector - connections and threads

Smith tomcat.ran...@gmail.com: Sorry, forgot: Tomcat 7.0.42 On Fri, Mar 7, 2014 at 3:59 PM, John Smith tomcat.ran...@gmail.com wrote: The NIO connector has two attributes from the standard HTTP Connector implementation, maxConnections and maxThreads with defaults of 1 and 200

RE: NIO connector - connections and threads

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? The connections won't

Re: NIO connector - connections and threads

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 connections that use my web application code waiting

RE: NIO connector - connections and threads

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, probably. Collecting some peak

Re: NIO connector - connections and threads

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. - Chuck

Re: NIO connector - connections and threads

2014-03-09 2:08 GMT+04:00 John Smith tomcat.ran...@gmail.com: Sorry, forgot: Tomcat 7.0.42 On Fri, Mar 7, 2014 at 3:59 PM, John Smith tomcat.ran...@gmail.com wrote: The NIO connector has two attributes from the standard HTTP Connector implementation, maxConnections and maxThreads

Re: NIO connector - connections and threads

Sorry, forgot: Tomcat 7.0.42 On Fri, Mar 7, 2014 at 3:59 PM, John Smith tomcat.ran...@gmail.com 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

NIO connector - connections and threads

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 have 200

(working) high load (100K+) websocket + NIO connector setting comparison on 1 Tomcat 7 instance

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

Re: (working) high load (100K+) websocket + NIO connector setting comparison on 1 Tomcat 7 instance

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

RE: (working) high load (100K+) websocket + NIO connector setting comparison on 1 Tomcat 7 instance

-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/2013 18:20, Bob DeRemer wrote

Re: (working) high load (100K+) websocket + NIO connector setting comparison on 1 Tomcat 7 instance

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 instance

Re: Using NIO connector with Apache Httpd 2.4

-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. When I was reading through the docs I

Re: Using NIO connector with Apache Httpd 2.4

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 to switch to AJP NIO connector. When I was reading through the docs I

Re: Using NIO connector with Apache Httpd 2.4

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 somebody who had experience with NIO connector let me know

Using NIO connector with Apache Httpd 2.4

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 somebody

Re: Using NIO connector with Apache Httpd 2.4

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. This made me think that NIO connector

Re: Using NIO connector with Apache Httpd 2.4

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 somebody who had experience with NIO

Re: Setting Nio connector in embedded tomcat7

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

Setting Nio connector in embedded tomcat7

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 refused. Same

Re: Setting Nio connector in embedded tomcat7

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 GET REST request

Re: Setting Nio connector in embedded tomcat7

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 ma...@apache.org wrote: On 23/04/2013 15:11, Praveen Peddi wrote

Re: Setting Nio connector in embedded tomcat7

/TomcatBaseTest.java Thanks Praveen On 4/23/13 Apr 23, 10:40 AM, Tribon Cheng tribon1...@gmail.com 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-Tomcat-7-td46523 51.html On Tue, Apr 23

Re: Setting Nio connector in embedded tomcat7

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 ppe...@kivasystems.com 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 it work

Re: Unix domain socket leak using NIO connector

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 someone else in the past, but with no response: http://mail-archives.apache.org

Re: Unix domain socket leak using NIO connector

, and this would indicate a problem in the NIO connector implementation. I've seen the same situation indicated by someone else in the past, but with no response: http://mail-archives.apache.org/mod_mbox/tomcat-users/201201.mbox/%3CCAJkSUv-DDKTCQ-pD7W=qovmph1dxexovcr+3mcgu05cqpt7...@mail.gmail.com%3E

Re: NIO connector issue: SEVERE: Error processing request

, 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 ke...@realtyserver.com wrote: Hi, We have a setup with Nginx load balancing between 2 clustered tomcat instances. 1

Re: NIO connector issue: SEVERE: Error processing request

-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

RE: NIO connector issue: SEVERE: Error processing request

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, 2013 at 9:34 AM

NIO connector issue: SEVERE: Error processing request

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

Re: NIO connector issue: SEVERE: Error processing request

. So my point is start troubleshooting on nginx side until you get response from some of the more experienced tomcat users/developers here :) And get ready to send your NIO connector and related nginx settings too I would say :) Igor

RE: HTTP NIO connector not supporting IPv6

-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: -Original Message- From: Daniel

Re: HTTP NIO connector not supporting IPv6

: 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: -Original Message- From: Daniel Mikusa [mailto:dmik...@vmware.com

Re: HTTP NIO connector not supporting IPv6

Regards, Aditi On Tue, Sep 11, 2012 at 7:30 PM, Jeffrey Janner jeffrey.jan...@polydyne.com wrote: -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

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: Thanks Dan, Jeff

Re: HTTP NIO connector not supporting IPv6

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 On Sep 12, 2012, at 1:29 AM, Aditi Sinha

HTTP NIO connector not supporting IPv6

. 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(defined in server.xml

Re: HTTP NIO connector not supporting IPv6

(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(defined in server.xml). What is the output of netstat -an? Can you include that as well? Dan *On modifying

RE: HTTP NIO connector not supporting IPv6

, 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 Hi, We have a web server hosted on Apache Tomcat Version

RE: HTTP NIO connector not supporting IPv6

-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 IPv4 and IPv6, including BIO, NIO, and native

Re: HTTP NIO connector not supporting IPv6

List' Subject: RE: HTTP NIO connector not supporting IPv6 Aditi - All connectors support both IPv4 and IPv6, including BIO, NIO, and native/APR. However, how you configure the connector will affect which protocol is supported. As far as I've been able to tell from empirical testing

Re: Odd NIO connector behavior

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 ma...@apache.org wrote: On 31/12/2011 16:35, Matthew Tyson

Re: Odd NIO connector behavior

On 29/12/2011 19:22, Matthew Tyson wrote: On Thu, Dec 29, 2011 at 11:07 AM, Pid p...@pidster.com wrote: On 29/12/2011 17:27, Matthew Tyson wrote: On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson matthewcarlty...@gmail.comwrote: On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr

Re: Odd NIO connector behavior

On Wed, Dec 28, 2011 at 1:04 AM, ma...@apache.org wrote: Matthew Tyson matthewcarlty...@gmail.com 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?

Re: Odd NIO connector behavior

On 31/12/2011 16:35, Matthew Tyson wrote: On Wed, Dec 28, 2011 at 1:04 AM, ma...@apache.org wrote: Matthew Tyson matthewcarlty...@gmail.com 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

Re: Odd NIO connector behavior

On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson matthewcarlty...@gmail.comwrote: On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr ste...@mayr-stefan.dewrote: Am 28.12.2011 10:04, schrieb ma...@apache.org: Matthew Tysonmatthewcarltyson@gmail.**com matthewcarlty...@gmail.com wrote: That's

Re: Odd NIO connector behavior

On Thu, Dec 29, 2011 at 11:07 AM, Pid p...@pidster.com wrote: On 29/12/2011 17:27, Matthew Tyson wrote: On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson matthewcarlty...@gmail.comwrote: On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr ste...@mayr-stefan.de wrote: Am 28.12.2011 10:04,

Re: Odd NIO connector behavior

On 29/12/2011 17:27, Matthew Tyson wrote: On Wed, Dec 28, 2011 at 6:22 PM, Matthew Tyson matthewcarlty...@gmail.comwrote: On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr ste...@mayr-stefan.dewrote: Am 28.12.2011 10:04, schrieb ma...@apache.org: Matthew Tysonmatthewcarltyson@gmail.**com

Re: Odd NIO connector behavior

On Thu, 2011-12-29 at 11:22 -0800, Matthew Tyson wrote: BIG SNIP 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

Re: Odd NIO connector behavior

On Thu, Dec 29, 2011 at 12:02 PM, Tim Watts t...@cliftonfarm.org wrote: On Thu, 2011-12-29 at 11:22 -0800, Matthew Tyson wrote: BIG SNIP How an empty 200 response could be generated without executing the logging statement here is a mystery. Do you still have that MonitoringFilter

Re: Odd NIO connector behavior

Matthew Tyson matthewcarlty...@gmail.com 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?

Re: Odd NIO connector behavior

Am 28.12.2011 10:04, schrieb ma...@apache.org: Matthew Tysonmatthewcarlty...@gmail.com 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

Re: Odd NIO connector behavior

On Wed, Dec 28, 2011 at 8:58 AM, Stefan Mayr ste...@mayr-stefan.de wrote: Am 28.12.2011 10:04, schrieb ma...@apache.org: Matthew Tysonmatthewcarltyson@gmail.**com matthewcarlty...@gmail.com wrote: That's right, there is an f5 load balancer. The valve is used to keep track of whether

Re: Odd NIO connector behavior

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:722)

Re: Odd NIO connector behavior

On Tue, Dec 27, 2011 at 11:11 AM, Mark Thomas ma...@apache.org 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)

Re: Odd NIO connector behavior

On Tue, Dec 27, 2011 at 1:31 PM, Stefan Mayr ste...@mayr-stefan.de 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 definitely improved

Re: Odd NIO connector behavior

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 getting better. No so glad to hear you are still having problems. The problems only crop up

Re: Odd NIO connector behavior

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 things are getting

Re: Odd NIO connector behavior

On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomas ma...@apache.org 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 definitely improved things

Re: Odd NIO connector behavior

Am 24.12.2011 19:33, schrieb Matthew Tyson: On Sat, Dec 24, 2011 at 1:06 AM, Mark Thomasma...@apache.org 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

Re: Odd NIO connector behavior

, 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 getting better. No so glad to hear you are still having problems. The problems only crop up after a couple minutes under some load (modest load

Odd NIO connector behavior

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

Advantage of using HTTP NIO Connector

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 * *

Re: Advantage of using HTTP NIO Connector

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 APR use one

Re: Advantage of using HTTP NIO Connector

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 better. BIO has slightly better raw performance than NIO

Re: Advantage of using HTTP NIO Connector

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

Re: Advantage of using HTTP NIO 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 connection. Since usually connections currently processing request, NIO and APR scale better. BIO has slightly better raw

RE: Nio Connector and self signed SSL certificate giving No client certificate chain in this request

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

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 ch...@christopherschultz.net 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

Nio Connector and self signed SSL certificate giving No client certificate chain in this request

Hello, I have tomcat 6.0.30 configured with NIOConnector (org.apache.coyote.http11.Http11NioProtocol) using latest JRE (1.6.0_23). The connector has 1 way SSL enabled, except for a URL that requires 2 way SSL. I do so using following security constraint in web.xml: security-constraint

Re: Nio Connector and self signed SSL certificate giving No client certificate chain in this request

On 04/02/2011 10:04, Parag Thakur wrote: Oddly, the same program works if I use org.apache.coyote.http11.Http11Protocol instead of org.apache.coyote.http11.Http11NioProtocol. Any idea what might be causing the NIO implementation to not work in this case? Does this have anything to do with SSL

Re: (Tomcat) Does NIO connector make a difference outside of 'Comet' ?

Caldarale, Charles R schrieb am 29.11.2010 um 22:47 (-0600): From: Michael Ludwig [mailto:mil...@gmx.de] can we say that: (a) blocking IO requires one thread (or, in some other server environments, one process) per socket Well, sort of. The actual requirement is one thread per

  1   2   >