Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000A4nT3IAJ&sfdc.override=1 project_key: JBPAPP6 The method javassist.util.proxy.RuntimeSupport.find2methods has a synch block, called indirectly by ProxyFactory.createClass(). It is a strong bottleneck for frameworks as Hibernate which can use it several times in a large set of data. More details in https://issues.jboss.org/browse/JASSIST-163
Link: Added: This issue Cloned from JBPAPP-9454
Link: Added: This issue relates to JASSIST-163
Labels: Removed: gss_required
Link: Added: This issue is related to AS7-5127
The https://issues.jboss.org/browse/JASSIST-163 fix needs more work. See discussion on JASSIST-163 & http://lists.jboss.org/pipermail/jboss-as7-dev/2012-July/006274.html
We don't have a javassist change yet that is safe to bring in.
https://hibernate.onjira.com/browse/HHH-5684 is related.
On hold until Javassist 3.17.0.GA released
Other AS modules that depend on javassist (via static module dependencies) are Weld, jbossws-native-core, scannotation.
Docs QE Status: Removed: NEW
Hibernate 4.1.9.Final stepped up to Javassist 3.17.1. All other EAP components, dependent on Javassist, tested and verified. EAP 6.1.0 will be based at least on 4.1.9, if not later. Marking this as resolved.
Reopening. Javassist 3.17.1 creates a regression: https://hibernate.onjira.com/browse/HHH-7884 https://issues.jboss.org/browse/JASSIST-189 Our current spec for EAP 6.1.0 is using Javassist 3.15.0-GA-redhat-2 until this is corrected.
Due to the Javassist regression with "bridge methods", I think its likely that we will retarget this issue to the next EAP 6.x release.
On hold for: https://issues.jboss.org/browse/JASSIST-183 https://issues.jboss.org/browse/JASSIST-189
Javassist 3.18.0.GA is released and will be updated in Hibernate upstream in https://hibernate.atlassian.net/browse/HHH-8288. We'll push into 6.2.0 after it's been through a few upstream releases. Scott and I would be more confident if it went through a Wildfly release as well.
*** Bug 977376 has been marked as a duplicate of this bug. ***
Propose for EAP 6.2
Moving to JPA component -- this needs upgraded in EAP itself.
Changing state to MODIFIED because the issue has been fixed in the component (Javassist). Created bug 1004020 to track merging the upgrade into EAP sources.
EAP 6.2.0.ER1