Bug 327877 - Tomcat 6.0.16 LTW Weaving Unable to pack method, jump (with opcode=154) is too far: 32720
Summary: Tomcat 6.0.16 LTW Weaving Unable to pack method, jump (with opcode=154) is t...
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: LTWeaving (show other bugs)
Version: 1.6.10   Edit
Hardware: Other Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 07:57 EDT by PASTUREL CLA
Modified: 2010-10-26 01:40 EDT (History)
1 user (show)

See Also:

Attachments
ajcore (9.04 KB, text/plain)
2010-10-15 07:57 EDT, PASTUREL CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description PASTUREL CLA 2010-10-15 07:57:32 EDT 
Created attachment 180946 [details]
ajcore

Version AspectJ 1.6.10
JDK 1.5.0_22 Sun HotSpot  64 bits Linux
Tomcat 6.0.16 with a J2EE application based on Spring and Struts2
Generate a ajcore joined as attachement.
Comment 1 PASTUREL CLA 2010-10-15 08:37:53 EDT 
To add more information:
this bug occurs with a call pointcut like call( public * mypackage..*.*(..))
and desappear with the execution pointcut. I want to have the caller method and the called method so i would need call pointcut.
Perhaps a problem with Spring weaving and AspectJ weaving ? I don't use the spring agent.
Comment 2 Andrew Clement CLA 2010-10-25 12:31:16 EDT 
I imagine one of the methods being affected is very large.  This affected method is then being inflated via weaving to the point where the jump cannot be captured correctly.  We currently have no support for dealing with this situation.
Comment 3 PASTUREL CLA 2010-10-26 01:40:14 EDT 
OK Thanks Andrew.
So as I understand, it is the calling method that is too big ( call pointcut doesn't run, execution pointcut runs).
You can close this bug, and perhaps add this behaviour in AspectJ document.