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
All ConnectionWatchdog debug logs are prefixed with a channel descriptor. This prefix is stored in the logPrefix field.
After a reconnect, the logPrefix is not updated, which leads to rather confusing log messages, because the channel descriptor in the log message does not represent the actually active channel.
For example in the following log message the current channel is actually /10.255.101.203:41124 -> /10.255.94.48:6381 while the log prefix shows /10.255.101.203:33545 -> /10.255.94.48:6381:
2017-11-09 10:12:40,958 [lettuce-nioEventLoop-5-15] DEBUG c.l.r.protocol.ConnectionWatchdog - [channel=0xeb2bc9b7, /10.255.101.203:33545 -> /10.255.94.48:6381, last known addr=/10.255.94.48:6381] channelInactive(ChannelHandlerContext(ConnectionWatchdog#0, [id: 0x8982a021, L:/10.255.101.203:41124 ! R:/10.255.94.48:6381]))
We found this bug in version 3.4.2.Final, but it is probably still relevant for latest SNAPSHOT.
The text was updated successfully, but these errors were encountered:
All ConnectionWatchdog debug logs are prefixed with a channel descriptor. This prefix is stored in the
logPrefix
field.After a reconnect, the
logPrefix
is not updated, which leads to rather confusing log messages, because the channel descriptor in the log message does not represent the actually active channel.For example in the following log message the current channel is actually
/10.255.101.203:41124 -> /10.255.94.48:6381
while the log prefix shows/10.255.101.203:33545 -> /10.255.94.48:6381
:We found this bug in version 3.4.2.Final, but it is probably still relevant for latest SNAPSHOT.
The text was updated successfully, but these errors were encountered: