Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-1603

Redo hashCode() and equals() methods in org.apache.logging.log4j.core.net.ssl classes.

Agile BoardAttach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.6.2
    • None
    • Core
    • None


      We have a few FindBugs warnings about hashCode() and equals(Object) methods in the package org.apache.logging.log4j.core.net.ssl classes.

      The first problem is that not all classes implement these method where some of the code expects it to like an equals() method calling another equals() method but there is not one and the behavior of Object.equals() kicks in.

      This change make it obvious where there are still issues: the behavior described above will only happen when the code path ends up in a JRE class which itself depends on Object.equals(), so you still get a FindBugs warning about that but it is no longer a warning about a class in our code. We can revisit how to best implement equals() for those classes later.

      It is possible that the warning is a false positive since the JRE could be using a subclass of the class FindBugs complains about.



          This comment will be Viewable by All Users Viewable by All Users


            ggregory Gary D. Gregory
            ggregory Gary D. Gregory




                Issue deployment