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
{{ message }}
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.
We have seen our Java application get stuck in what seems to be an infinite loop where it consumes 100% CPU on one core when using the below configuration.
The last time it happened it correlated somewhat with our Graylog server going offline. We've let it run for awhile to see if it would recover but it doesn't seem like it, is there some kind of request/read/write timeout missing somewhere?
SSL handshake is now guarded against getting stuck because of an invalid socket state by applying the connect timeout. SSL handshake is also canceled if the socket got disconnected in during the handshake.
We have seen our Java application get stuck in what seems to be an infinite loop where it consumes 100% CPU on one core when using the below configuration.
The last time it happened it correlated somewhat with our Graylog server going offline. We've let it run for awhile to see if it would recover but it doesn't seem like it, is there some kind of request/read/write timeout missing somewhere?
Ran
strace
on the process and could observe this:Stacktrace
https://gist.github.com/rbjorklin/28cf847c1bb673620c62cf3781b92737
Version
logstash-gelf: 1.11.1
logback: 1.2.3
slf4j: 1.7.25
The text was updated successfully, but these errors were encountered: