https://issues.apache.org/bugzilla/show_bug.cgi?id=54113
--- Comment #5 from gar...@motorweb.co.nz ---
(In reply to comment #4)
Right, that makes sense. Unfortunately it's not possible to determine from our
stack trace which fo was being used, but it's quite likely somewhere in our
codebase we ha
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113
Alex Giotis changed:
What|Removed |Added
CC||alex.gio...@gmail.com
--
You are re
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113
--- Comment #4 from Alex Giotis ---
Gareth, I believe that this is a bug exposed by fixing some equals/hashcode
implementations. Those changes were introduced during the refactoring of
PropertyCache (as you wrote) and I also believe that th
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113
gar...@motorweb.co.nz changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #3 from gar
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113
--- Comment #2 from gar...@motorweb.co.nz ---
Created attachment 29665
--> https://issues.apache.org/bugzilla/attachment.cgi?id=29665&action=edit
Thread dump snippet
--
You are receiving this mail because:
You are the assignee for the bu
https://issues.apache.org/bugzilla/show_bug.cgi?id=54113
Alex Giotis changed:
What|Removed |Added
Status|NEW |NEEDINFO
OS|
