[Jedis 3.x] HostAndPort should not include log object, otherwise may cause problem in java agent scenarios

[renyingxin]

Problem description:
HostAndPort should not include log object, otherwise may cause problem in java agent scenarios

Problem detail:
In java agent scenarios, we may intercept the redis.clients.jedis.Jedis constructor and proccess the initialization event，we may need proccess the HostAndPort object, but this will cause all slf4j loggers begin to init。
if there are some other agent try to intercept the slf4j loggers, they may not take effect as the logger object is already initializated.

suggestion:
https://github.com/redis/jedis/blob/3.x/src/main/java/redis/clients/jedis/HostAndPort.java
I think should remove logger related from this info object, as you did in jedis 4.3.x.
I hope you can release new 3.x version and solve this problem, thanks~

[ggivo]

Hi, @renyingxin
As you already found the logger got removed with #3008 and this change got released as part of 4.3 release.

Could you elaborate on the use case mentioned around java agent scenarios. More detailed explanation of how you use Jedis in this scenario, and providing an example, will help us better understand this scenario and prioritize it in the future.

We do not have a planned release of 3.x. Since you already found that the logger got removed with 4.3 version, I assume there are other drivers to not use a more recent version?

[renyingxin]

Could you elaborate on the use case mentioned around java agent scenarios. More detailed explanation of how you use Jedis in this scenario, and providing an example, will help us better understand this scenario and prioritize it in the future.

Hi, we use sermant as our java agent framework, https://github.com/sermant-io/Sermant

The Agent would be serveral fat jars (including all the dependency classes inside), we need to check the jedis version before we try to enhance it. different jedis version may need different proccess, so we use some info class to figure out the version, eg .HostAndPort does not exist in jedis older versions, so can be used to determin the jedis version

we have already used other classes to distinguish between different jedis versions, to work around this problem.

[ggivo]

@renyingxin
Thanks for getting back. Our hands are full right now and we have not planned 3.x release at that point, it will take some time before we get to this one.