[jboss-jira] [JBoss JIRA] (ELY-1324) Authentication is not cached properly if the callback handler does not implement equals()/hashCode()

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/ELY-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas moved JBREM-1338 to ELY-1324:
--------------------------------------------

     Project: WildFly Elytron  (was: JBoss Remoting)
         Key: ELY-1324  (was: JBREM-1338)
    Workflow: GIT Pull Request workflow   (was: classic default workflow)


> Authentication is not cached properly if the callback handler does not implement equals()/hashCode()
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ELY-1324
>                 URL: https://issues.jboss.org/browse/ELY-1324
>             Project: WildFly Elytron
>          Issue Type: Bug
>            Reporter: Stuart Douglas
>
> If the callback handler does not implement equals()/hashCode() then AuthenticationConfiguration objects will not be considered equal (in the case where a new one is being created each time), which will result in a memory leak in org.jboss.remoting3.ConnectionPeerIdentityContext#futureAuths, as well as authentication being attempted for every request. This can be observed by adding a loop to org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase#testRemoteLookup
> I think this is a fairly serious issue, as I think there will be a lot of handler out there that do not meet this requirement, and it causes both a serious performance regression due to repeated auth, as well as a memory leak that can crash the JVM. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)