Thanks for the response. Is there a way to confirm if it is the garbage collector that is performing the socket close in this scenario? I know the specific routine where the close seems to be happening. Any other information that can help confirm the same would be great.
Thanks.