I had another thought about that issue. We're compensating at this moment something that happens between two 3rd party libs and I'm a fan of removing the root cause. I'm releasing on Thursday 3.3.Beta1 and end of August 3.3.Final of lettuce. 3.3 provides an answer to the re-use of RedisClient/OGM-880 and I'd like to address the netty 4.0.26 issue within lettuce.

The cost of the own-netty-jar's solution is a follow-up ticket to remove the own netty jars. The solution within the Redis driver is permanent, but the cost is waiting for the beta/final. Let's have tomorrow a chat about this topic to find the best solution.