> Source: [sk180364](https://support.checkpoint.com/results/sk/sk180364)

# sk180364 - Gateway cluster member prematurely expires half-closed TCP connections when SecureXL is enabled

| Property | Value |
|----------|-------|
| Solution ID | sk180364 |
| Date Created | 2022-12-11 |
| Last Modified | 2024-03-07 |
| Technical Level | General |
| Products | Security Gateway, Scalable Platforms |
| Versions | R81.10 (EOS), R81 (EOS), R81.10 (EOS) |
| OS | Gaia |

## Symptoms

- * Users are randomly disconnected when they access web applications that are behind a Cluster or Maestro configuration with SecureXL enabled.
* Traffic logs in SmartConsole show that the first packet is not a Syn packet. This means that there are out of state drops.
* The kernel debug and connections table show that TCP connections expire 15 seconds after one side closes the connection.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 82
* [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 79
* [Jumbo Hotfix Accumulator for R80.40](https://sc1.checkpoint.com/documents/Jumbo_HFA/R80.40/Default.htm) starting from Take 196

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

<br />

Also this workaround is available:

1. Follow the procedure in [sk137672](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk137672) to reset the value of the *tcp_half_closed_timeout* parameter to `1`.
2. Install policy for all cluster members.  
   The cluster members enforce the default timeout of 3600 seconds for half-closed TCP connections.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content