[jboss-jira] [JBoss JIRA] (JBRULES-3220) AbstractHashTable resize gets corrupted

[RH Bugzilla Integration (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632413#comment-12632413 ] 

RH Bugzilla Integration commented on JBRULES-3220:
--------------------------------------------------

Mark Proctor <mproctor at redhat.com> made a comment on [bug 743540|https://bugzilla.redhat.com/show_bug.cgi?id=743540]

I have now fixed this in master. However I noticed the previous incorrect fix was not cherry-picked to 5.2.x either.

The commits are listed in jira, under source commits. As this is now late stage and you need control over git, I'll leave you to cherry pick these. Even though the original commit is wrong, you'll have to cherry-pick that first to get the correct diff ordering. My later commit fixes

https://issues.jboss.org/browse/JBRULES-3220
                
> AbstractHashTable resize gets corrupted
> ---------------------------------------
>
>                 Key: JBRULES-3220
>                 URL: https://issues.jboss.org/browse/JBRULES-3220
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Geoffrey De Smet
>            Assignee: Mark Proctor
>
> see MiscTest.testGetFactHandle() which is a regression test for that issue.
> ----
> The reason for this is that the resize method uses the comparators rehash method. In some cases the key caches a rehashed value and in some it doesn't. Causing an already rehashed number to be rehashed again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira