Bug 160674

Summary:	SAP app server classloader configuration prevents bcel classloaderrepository caching
Product:	[Tools] AspectJ	Reporter:	Andrew Clement <aclement>
Component:	Compiler	Assignee:	Andrew Clement <aclement>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3
Version:	DEVELOPMENT
Target Milestone:	1.5.3
Hardware:	PC
OS:	All
Whiteboard:

Description Andrew Clement

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

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

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.