Bug 779698 (SOA-2062) - Backport https://jira.jboss.org/jira/browse/JASSIST-66 to SOA-P 4.3.0
Summary: Backport https://jira.jboss.org/jira/browse/JASSIST-66 to SOA-P 4.3.0
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2062
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: EAP
Version: 4.3 CP02
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP05
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 11:09 UTC by Stelios Koussouris
Modified: 2011-04-20 12:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-20 12:18:11 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2062 0 None None None Never

Description Stelios Koussouris 2010-04-30 11:09:18 UTC
Date of First Response: 2010-06-08 06:11:34
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=766063&gid=1354
project_key: SOA

This JavaAssist JIRA indicates that it has been fixed in Java Assist 3.9.0 which is in EAP 5/SOA-P 5

we have a customer asking to backport it to SOA-P 4.3.0

Comment 1 Stelios Koussouris 2010-04-30 11:09:42 UTC
Link: Added: This issue depends JBPAPP-4204


Comment 2 Stelios Koussouris 2010-04-30 11:10:08 UTC
Link: Added: This issue incorporates JASSIST-66


Comment 4 Anne-Louise Tangring 2010-10-27 19:08:36 UTC
The corresponding jbpapp jira is marked resolved, this will be picked up as part of picking up the next EAP CP release. (only if the validation fails in EAP would we be unable to resolve this)

Comment 5 nwallace 2011-03-17 14:26:11 UTC
This is cleared in EAP 4.3 CP09

Comment 6 David Le Sage 2011-03-21 01:14:42 UTC
Release Notes Docs Status: Added: Not Yet Documented
Writer: Added: dlesage


Comment 7 David Le Sage 2011-04-01 04:31:24 UTC
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2062

A race condition could make the RuntimeSupport.DefaultMethodHandler.invoke() method throw a run-time exception.  This occurred if Hibernate was being used under heavy load conditions.  To fix this problem, Java Assist 66 has been backported. As a result, users will no longer encounter this exception.


Comment 8 David Le Sage 2011-04-01 04:33:48 UTC
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2062

A race condition could make the RuntimeSupport.DefaultMethodHandler.invoke() method throw a run-time exception.  This occurred if Hibernate was being used under heavy load conditions.  To fix this problem, Java Assist 66 has been backported. As a result, users will no longer encounter this exception. Added: https://issues.jboss.org/browse/SOA-2062

A race condition could occur if Hibernate was being used under heavy load. This race condition made the RuntimeSupport.DefaultMethodHandler.invoke() method throw a run-time exception.  To fix this problem, Java Assist 66 has been backported. As a result, users will no longer encounter this exception.


Comment 9 David Le Sage 2011-04-01 05:02:58 UTC
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2062

A race condition could occur if Hibernate was being used under heavy load. This race condition made the RuntimeSupport.DefaultMethodHandler.invoke() method throw a run-time exception.  To fix this problem, Java Assist 66 has been backported. As a result, users will no longer encounter this exception. Added: https://issues.jboss.org/browse/JBPAPP-4204

A race condition could occur if Hibernate was being used under heavy load. This race condition made the RuntimeSupport.DefaultMethodHandler.invoke() method throw a run-time exception.  To fix this problem, Java Assist 66 has been backported. As a result, users will no longer encounter this exception.


Comment 10 Jiri Pechanec 2011-04-20 12:18:11 UTC
Verified in ER2


Note You need to log in before you can comment on or make changes to this bug.