Diagnostic Generated - The underlying Tcp connection is closed

[KoalaBear84]

I'm getting 'strange' errors since yesterday. I'm using the experimental async processing. When a user request a lot of downloads it looks like something is failing.

I'm now going to only show 1 of this type of message (per user), because maybe the logging takes too long and breaks it.

2025-10-18 12:01:32.668 +02:00 [INF] EnqueueDownloadAction called for XXXXXXXX at XXX.XXX.XXX.XXX:12063 with filename Ebooks\Tralala01.epub
2025-10-18 12:01:32.668 +02:00 [INF] EnqueueDownloadAction called for XXXXXXXX at XXX.XXX.XXX.XXX:12063 with filename Ebooks\Tralala02.epub

.. Lots of EnqueueDownloadAction

2025-10-18 12:01:42.394 +02:00 [WRN] Diagnostic Generated. Level: "Warning", Timestamp: 2025-10-18T10:01:42.3948342Z, Message: Error handling peer message: QueueDownload from XXXXXXXX (XXX.XXX.XXX.XXX:12063); Invalid attempt to send to a disconnected or transitioning connection (current state: Disconnecting)
2025-10-18 12:01:42.400 +02:00 [WRN] Diagnostic Generated. Level: "Warning", Timestamp: 2025-10-18T10:01:42.3991788Z, Message: Error handling peer message: QueueDownload from XXXXXXXX (XXX.XXX.XXX.XXX:12063); The underlying Tcp connection is closed
2025-10-18 12:01:42.438 +02:00 [WRN] Diagnostic Generated. Level: "Warning", Timestamp: 2025-10-18T10:01:42.4386740Z, Message: Error handling peer message: QueueDownload from XXXXXXXX (XXX.XXX.XXX.XXX:12063); Invalid attempt to send to a disconnected or transitioning connection (current state: Disconnecting)
2025-10-18 12:01:42.438 +02:00 [WRN] Diagnostic Generated. Level: "Warning", Timestamp: 2025-10-18T10:01:42.4386973Z, Message: Error handling peer message: QueueDownload from XXXXXXXX (XXX.XXX.XXX.XXX:12063); Invalid attempt to send to a disconnected or transitioning connection (current state: Disconnecting)
2025-10-18 12:01:42.439 +02:00 [WRN] Diagnostic Generated. Level: "Warning", Timestamp: 2025-10-18T10:01:42.4393815Z, Message: Error handling peer message: QueueDownload from XXXXXXXX (XXX.XXX.XXX.XXX:12063); The underlying Tcp connection is closed
2025-10-18 12:01:42.438 +02:00 [WRN] Diagnostic Generated. Level: "Warning", Timestamp: 2025-10-18T10:01:42.4386915Z, Message: Error handling peer message: QueueDownload from XXXXXXXX (XXX.XXX.XXX.XXX:12063); The underlying Tcp connection is closed

And also got two times that the whole client failed. I'm not sure about the position, will record that next time (I'm not on seeing it through the phone) :)

[jpdillingham]

This is expected behavior when a connection disconnects; any attempt to read from or write to a failing connection throws the exceptions you see here.

Make sure you are setting WriteBufferSize for peer connections to int.MaxValue, the connection might have been disconnected if there were a lot of writes backed up.

[KoalaBear84]

It looks like the connection wasn't closed, at least I thought it might had to do with the delay in processing and that something else out the SoulSeekClient killed the connection.

Ahh, I had the writeQueueSize things to MaxValue:

    raiseEventsAsynchronously: true,
    transferConnectionOptions: new ConnectionOptions(
        readBufferSize: 128 * 1024,
        writeBufferSize: 128 * 1024,
        writeQueueSize: int.MaxValue,
        connectTimeout: (int)TimeSpan.FromSeconds(60).TotalMilliseconds,
        inactivityTimeout: (int)TimeSpan.FromSeconds(120).TotalMilliseconds
    )

[KoalaBear84]

But it should be WriteBufferSize?

[jpdillingham]

That looks correct