Bug 160674 - SAP app server classloader configuration prevents bcel classloaderrepository caching
Summary: SAP app server classloader configuration prevents bcel classloaderrepository ...
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: 1.5.3   Edit
Assignee: Andrew Clement CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-12 10:12 EDT by Andrew Clement CLA
Modified: 2006-10-13 02:53 EDT (History)
0 users

See Also:

Attachments
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 Andrew Clement CLA 2006-10-12 10:12:01 EDT 
Recently we upgraded the Bcel classloaderrepository to allow caching (by URL) of the classes that get loaded.  The cached entries could even be shared by multiple weavers in the same VM.  Unfortunately the SAP netweaver configuration of classloaders doesn't like this and so we need to be able to revert to the poorly performing old strategy on this appserver.
Comment 1 Andrew Clement CLA 2006-10-12 12:19:18 EDT 
Although the cache itself is fully configurable (can already be switched off) - it is not the activity of 'caching' that is the problem here, it is in the use of a URL to identify the class. getResource() appears to be causing us problems in this environment.
Comment 2 Andrew Clement CLA 2006-10-13 02:53:42 EDT 
fix is in.  now configurable - can be switched OFF in certain environments

-Xset:bcelRepositoryCaching=false

test in for the option, but can't actually 'test' the problem since creating a similar classloader hierarchy mess is too tricky.