Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How do I ensure that the stack closes TCP connections after transaction completion?

0
Posted

How do I ensure that the stack closes TCP connections after transaction completion?

0

The following two configuration parameters instruct the stack to close TCP connections after a linger period: gov.nist.javax.sip.CACHE_SERVER_CONNECTIONS=false Default is true. Does reference counting for server transactions if false and releases resources after refcount goes to 0. gov.nist.javax.sip.CACHE_CLIENT_CONNECTIONS=false Default is true. Does reference counting for client transactions and releases socket and thread resources after refcount goes to 0. Setting to false will close the connection and release any threads and buffers after all transactions that use the connection have terminated and a keepalive period (currently 32 sec) has expired. In some circumstances (eg. if you are supporting NAT via tcp, then it may be appropriate not to close server connections). Defaults for these are true – which may be appropriate to do if you are burrowing through firewalls using tcp.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123