# TCP Server Failure event generating taking 120 sec

**URL:** https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658
**Category:** General
**Created:** [13 December 2023 06:48 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658 "2023-12-13T06:48:03Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![shershah](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@shershah](https://discourse.nodered.org/u/shershah)
#### Post date: [13 December 2023 06:48 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/1 "2023-12-13T06:48:03Z")

</div>

Hi All,

I am connected to tcp server to do write operation. When Server is disconnected and I perform write operation, I am publishing failure response but It takes 2 min to capture failure response by catch node. I don't see any such configuration. Using status Node I am able to generate server disconnect response but I have to send failure response on every server write operation.

Please refer below url for the flow example.

> [@NodeRed TCP OUT Node Success Response](https://discourse.nodered.org/t/nodered-tcp-out-node-success-response/81256/14):
>
> [quote="Steve-Mcl, post:13, topic:81256, full:true"] Sorry, that sample flow is not entirely clear what you are expecting to send to MQTT AFTER success/fail. For example, you have not created a tcp-in -\> send\_fake\_but\_valid\_data -\>tcp-out I am sending back the exact same request json with additional variables of successCode in case of success and errorcode in case of error. I have added sample response json in function node Good - ok. I understand that. If you get a "list of sensors" t…

Thanks,  
Shershah

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [13 December 2023 11:37 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/2 "2023-12-13T11:37:43Z")

</div>

I am not certain, but I suspect that is not under the control of node-red, it may be the time that your OS waits before signalling the timeout.

Perhaps you could use a ping node to monitor whether the server is connected.

---

<div class="post-metadata">

### Author: ![shershah](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@shershah](https://discourse.nodered.org/u/shershah)
#### Post date: [13 December 2023 11:45 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/3 "2023-12-13T11:45:04Z")

</div>

Hi Colin,  
Even when the server is disconnected, it is taking time to respond.

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/2/b299564f5b98290c5f8038fab06b8e6772f7e764.png)

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [13 December 2023 11:48 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/4 "2023-12-13T11:48:40Z")

</div>

> [@shershah](#):
>
> Even when the server is disconnected, it is taking time to respond.

Possibly it thinks it should try again, since you have asked it to do so.  
You can easily use the disconnected status to block requests to the node if you want to do that.

---

<div class="post-metadata">

### Author: ![shershah](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@shershah](https://discourse.nodered.org/u/shershah)
#### Post date: [13 December 2023 12:17 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/5 "2023-12-13T12:17:06Z")

</div>

When The server is disconnected, I just dont want to block the request. I want to send back the failure message which I am doing through catch block but it is taking 2 minutes to catch the exception using catch block

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [13 December 2023 13:18 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/6 "2023-12-13T13:18:53Z")

</div>

> [@shershah](#):
>
> it is taking 2 minutes

As I said, I suspect that is an OS networking function rather node-red, though I may be wrong.  
You could also use the disconnected status to trigger the failure message.

---

<div class="post-metadata">

### Author: ![shershah](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@shershah](https://discourse.nodered.org/u/shershah)
#### Post date: [13 December 2023 16:45 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/7 "2023-12-13T16:45:33Z")

</div>

Disconnected status is triggered only once.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [13 December 2023 16:59 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/8 "2023-12-13T16:59:20Z")

</div>

It should be triggered every time it goes from connected to disconnected.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [11 February 2024 16:59 UTC](https://discourse.nodered.org/t/tcp-server-failure-event-generating-taking-120-sec/83658/9 "2024-02-11T16:59:52Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
