[ModuleClassLoader@4e730222] info register classloader org.apache.felix.framework.ModuleImpl$ModuleClassLoader@4e730222
[ModuleClassLoader@4e730222] info using configuration file:/Library/Tomcat/apache-tomcat-6.0.35-jira/webapps/jira/WEB-INF/lib/ia-aspects-0.0.1-SNAPSHOT.jar!/META-INF/aop.xml
[ModuleClassLoader@4e730222] info register aspect com.ia.UseProfiler
Jul 29, 2013 1:48:25 PM org.aspectj.weaver.tools.Jdk14Trace error
SEVERE: register definition failed
java.lang.RuntimeException: Cannot register non aspect: com$ia$UseProfiler , com.ia.UseProfiler
implies that the com.ia.UseProfiler aspect couldn't be found. AspectJ isn't trying anything magic, it is using the classloader getResource()/getResourceAsStream() type operations to access the aop.xml and the class files (for the aspect). If the classloader in question is choosing to do some unusual delegation or enforcing some rules that affect visibility of the aspect classes through those methods, it can manifest like this.
Does that felix classloader offer any extra configuration options?
> I have no access to change/modify the code
Does that just mean you don't have the source? If you have access to the classes you could just binary weave the aspect into the jars before you start it (no source code for the app required):
ajc -inpath inputjar.jar UseProfiler.aj -outjar wovenjar.jar
This means you don't need any LTW and don't need to worry about funky classloaders.
cheers,
Andy