Transaction Timeout

[tyler811]

What is the transaction timeout in the DCom Configuration used for?

 

[spidey07]

I don't know that exact application/protocol, but universally a timeout means a timer expired. Didn't complete the transaction in the time expected, didn't hear back from a server after a number of retires, server to busy to respond to your request, etc.

 

[tyler811]

I don't know that exact application/protocol, but universally a timeout means a timer expired. Didn't complete the transaction in the time expected, didn't hear back from a server after a number of retires, server to busy to respond to your request, etc.

Thanks Spidey 🙂

So if it times out could this cause an error and bring down a program or wireless connection?

 

[spidey07]

Thanks Spidey 🙂

So if it times out could this cause an error and bring down a program or wireless connection?

Totally depends on the application. Some will give up and fail, others will try to re-establish the TCP connection/socket. It it's an actual TCP timeout then something is pretty wrong because that means the TCP socket was broken and TCP will do it's best to retry and retry until - timeout, I'm done.

What the app does with that broken socket, is up to the app. For many the app will indeed break. It really all does depend on the app and how it uses the protocol. There's no expected behavior from layer7 (the app), it's underlying foundation (TCP) is gone.