- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Time between Syn & Established
Operating System - Linux
1758269
Members
2538
Online
108868
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 10:21 AM
тАО10-30-2009 10:21 AM
We had an issue yesterday where Apache reached MaxClient limit on all our web servers. Though we couldn't determine the coz at that time, in theory we think it happened because of a ACL issue between our web server and app server.
Because web server(through mod_jk connector) wasn't able to talk to app server and the syn packed got dropped on the firewall, the sessions kept increasing and ultimately maxed out.
I want to know if we have a Linux parameter which can be tuned for the time between a syn request and establish. Can we lower that time between those two state?
Thanks,
Allan.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 11:09 AM
тАО10-30-2009 11:09 AM
Re: Time between Syn & Established
Can you help on this please!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 11:20 AM
тАО10-30-2009 11:20 AM
Solution
A TCP connection has no timed delays in the transition from SYN_SENT to ESTABLISHED. This transition can happen as soon as the listening endpoint sends the SYN+ACK packet.
Without the SYN+ACK packet, the transition cannot happen at all: this is because the SYN and SYN+ACK packets are used to determine the initial TCP Sequence Numbers, which must be known by both endpoints or the connection won't work. You cannot establish a connection with something that does not answer at all: no amount of tuning and tweaking can make this happen.
If your mod_jk cannot talk to the application server in a reasonable time, the only possibility is to time out and let Apache generate an error response to the client, ending the client-side request and freeing the Apache client slot.
This can be set in mod_jk workers.properties file, using the worker..socket_timeout and worker..socket_connect_timeout settings.
By default both settings are zero, which means no timeout at all: mod_jk will wait forever for the application server's answer. Of course this causes the client-side sessions to pile up, until the MaxClients limit is reached.
If either of these timeouts are reached, mod_jk will try to re-establish the connection and try again one more time (the number of retries is adjustable too). If the retry attempt fails too, mod_jk will return an error to Apache. At that point, Apache will generate an error page, terminating the client's HTTP request and thus freeing up Apache's client slot.
MK
Without the SYN+ACK packet, the transition cannot happen at all: this is because the SYN and SYN+ACK packets are used to determine the initial TCP Sequence Numbers, which must be known by both endpoints or the connection won't work. You cannot establish a connection with something that does not answer at all: no amount of tuning and tweaking can make this happen.
If your mod_jk cannot talk to the application server in a reasonable time, the only possibility is to time out and let Apache generate an error response to the client, ending the client-side request and freeing the Apache client slot.
This can be set in mod_jk workers.properties file, using the worker.
By default both settings are zero, which means no timeout at all: mod_jk will wait forever for the application server's answer. Of course this causes the client-side sessions to pile up, until the MaxClients limit is reached.
If either of these timeouts are reached, mod_jk will try to re-establish the connection and try again one more time (the number of retries is adjustable too). If the retry attempt fails too, mod_jk will return an error to Apache. At that point, Apache will generate an error page, terminating the client's HTTP request and thus freeing up Apache's client slot.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 02:14 PM
тАО10-30-2009 02:14 PM
Re: Time between Syn & Established
Super Solid Answer, just what I needed.
Thanks so much!
Allan.
Thanks so much!
Allan.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP