Closed VladimirRudt closed 5 days ago
Sorry, I have not been able to reproduce this.
[ReqSeq:19] Response completed with failure (error reading a body from connection) (0x0)
The error message in the log says “error reading a body from connection”. This is most likely due to the network connection being disconnected for some reason.
[ReqSeq:2] Response completed with failure (client error (SendRequest): http2 error) (0x0)
On the other hand, the error message ”client error (SendRequest): http2 error" is an error that is output when sending a request and before receiving a response.
I'm sorry, but at this point I cannot say for certain whether this is due to the network connection being disconnected or a library bug.
@mayuki Seems the reason is exactly bad connection. I could easily reproduce an issue simply turning off the server during streaming. After that I cought RpcException
with Unavailable
status.
The only one question, why Unity logger writes inner exception instead of original one.
What I see in during debug:
What Debug.LogException writes:
Hi @mayuki, we faced a tricky issue. It might be not a bug, but we cannot be sure without your confirmation.
Scenario of the issue. I added references to the request numbers from the attached log file.
[ReqSec:19]
that provide us with camera preview[ReqSec:20]
which changes parameters of the camera previewSometimes the server stream crashes during the second operation and all running requests/streams are cancelled. After that the client resets the connection and closes the socket.
We use a not very stable connection to the server on another continent, and this may be the reason for the connection being dropped. We also have some other client and duplex streams
[ReqSec:3, 2, 5, 6]
running in the background and adding a small load as well. But the missing error code is the reason we are not sure that issues related to the bad connection:2024.08.20 15:31:59.693 14770 14873 Info Unity [ReqSeq:19:State:0x35] Response completed: Reason=Error; H2ErrorCode=0x0
This is our client handler configuration:
We are using YetAnotherHttpHandler v1.5.2. As far as I know, the latest version v1.5.3 does not have any changes that could fix this.
Logs from the client side. We launch it on Android logcat.txt
Logs on server side regarding camera preview stream:
Other streams which waited for response just failed: