'Why so many Debug Logs with "setHandshakeSuccess" in vertx / quarkus?
we are evaluating quarkus and deployed one prototype with the log level DEBUG and just let it run for a few days. Our Logstash collapsed because of a java.lang.ArithmeticException and while investigating we saw so many setHandshakeSuccess logs from the new quarkus-web-service.
To be exact: 2600 logs every 5 minutes.
No one even uses the web service. It should be running idle and not produce so many logs.
Can anyone tell us whether this is normal behavior?
Example Log:
"message": "[id: 0x9869d583, L:/XX.XXX.XXX.XXX:8181 - R:/XX.XXX.X.XXX:49892] HANDSHAKEN: protocol:TLSv1.3 cipher suite:TLS_AES_256_GCM_SHA384"
"SourceClassName": "io.netty.handler.ssl.SslHandler",
"Thread": "vert.x-eventloop-thread-1",
The port number at the end of the second ip varies but there is no network traffic.
Does this message only mean that quarkus is checking ALL OF the available ports for traffic?
quarkus.platform.version = 2.8.1.Final
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|