Projects tigase _server server-core Issues #337
Wrong logging level for TLSWrapper (#337)
Closed
Artur Hefczyc opened 1 decade ago

Our logs are filled with log entry like this:

2014-06-17 05:52:20.170 [pool-18-thread-3]  TLSWrapper.<init>()               INFO:     Created client TLSWrapper. Protoc ols:[SSLv2Hello, TLSv1, TLSv1.1, TLSv1.2]; Ciphers:[TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_C BC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256,  TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH E_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_ CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]

I do not think we need it. Please change logging level to much lower priority so it is printed only in debug mode.

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
RedmineID
2009
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#337
Please wait...
Page is in error, reload to recover