li4wang commented on pull request #1802:
URL: https://github.com/apache/zookeeper/pull/1802#issuecomment-1080880951
Thanks @eolivelli and others for getting this in. Really appreciated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
li4wang commented on pull request #1802:
URL: https://github.com/apache/zookeeper/pull/1802#issuecomment-1075442960
Any updates on this @eolivelli ? We are in the process of deploying 3.7 to
production. It would be great if this issue can be addressed. Please let me
know if anything I can
li4wang commented on pull request #1802:
URL: https://github.com/apache/zookeeper/pull/1802#issuecomment-1065398600
Thanks for looking into this @eolivelli
For the Vulnerability issue reported from slf4j-log4j12, how about updating
slf4j version from `1.7.30` to `1.7.35`? Another th
li4wang commented on pull request #1802:
URL: https://github.com/apache/zookeeper/pull/1802#issuecomment-106472
Would it be possible to get this PR merged soon? Please let me know if
anything I can help with.
--
This is an automated message from the Apache Git Service.
To respond to
li4wang commented on pull request #1802:
URL: https://github.com/apache/zookeeper/pull/1802#issuecomment-1049279741
> The only issues I saw was the removal of the JMX MBean stuff, but
ZooKeeper should already handle that fine.
Yeah, I noticed JMX MBean stuff was removed from reload4
li4wang commented on pull request #1802:
URL: https://github.com/apache/zookeeper/pull/1802#issuecomment-1049242463
> Note that reload4j is not 100% compatible with Log4j 1.2.
According to the Reload4j website, reload4j is a fork of log4j1.2 and
supposed to be a drop-in replacement
