You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the read idle timeout is reached then it appears as though the PublisherAsStream class then returns -1 on its next read method. If this happens when the micronaut.server.idle-timeout is reached then I suppose it should do the same thing.
Actual Behaviour
The thread gets stuck at: /io/micronaut/http/netty/PublisherAsBlocking.java:160. The read idle timeout also doesn't seem to trigger in this circumstance.
Expected Behavior
If the read idle timeout is reached then it appears as though the
PublisherAsStream
class then returns -1 on its next read method. If this happens when themicronaut.server.idle-timeout
is reached then I suppose it should do the same thing.Actual Behaviour
The thread gets stuck at:
/io/micronaut/http/netty/PublisherAsBlocking.java:160
. The read idle timeout also doesn't seem to trigger in this circumstance.Steps To Reproduce
I found that the above code reproduces the problem as long as I used a 90kb worth of data. For smaller data it seemed to work better.
Environment Information
Linux
Openjdk-23
Example Application
No response
Version
4.6.3
The text was updated successfully, but these errors were encountered: