I am trying out the Netbeans 6 profiler 1.6.2 with an webapp deployed to Weblogic 9.2. Our application uses AspectJ5
(1.5.4) and I got thousands of "AspectJ5 does not weave hotswapped class" exception during startup. For example:

<Mar 18, 2008 1:20:29 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM)
Client VM Version 1.5.0_12-b04 from Sun Microsystems Inc.>
java.lang.Exception: AspectJ5 does not weave hotswapped class (sun/misc/Signal$1)
        at org.aspectj.weaver.loadtime.ClassPreProcessorAgentAdapter.transform(ClassPreProcessorAgentAdapter.java:55)
        at sun.instrument.TransformerManager.transform(TransformerManager.java:122)
        at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:155)
        at org.netbeans.lib.profiler.server.system.Classes.doRedefineClasses(Native Method)
        at org.netbeans.lib.profiler.server.system.Classes.redefineClasses(Classes.java:142)
        at org.netbeans.lib.profiler.server.ProfilerInterface.instrumentMethodGroupNow(ProfilerInterface.java:1077)
        at org.netbeans.lib.profiler.server.ProfilerInterface.getAndInstrumentClasses(ProfilerInterface.java:633)
        at org.netbeans.lib.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:871)
        at sun.misc.Signal.dispatch(Signal.java:189)

From the stack trace, it seemed to me that Netbeans profiler is also using a aspectj5 agent for load time weaving. 

In our startup script, the aspectJ and netbeans agents are configured as following:

@REM ============== ASPECTJ Startup Option =================
set ASPECTJ_OPTION=-javaagent:c:\tools\aspectj1.5.4\lib\aspectjweaver.jar
@REM =======================================================

SET JAVA_OPTIONS=-agentpath:"C:\Program Files\NetBeans
6.0\profiler2\lib\deployed\jdk15\windows\profilerinterface.dll=\"C:\Program Files\NetBeans 6.0\profiler2\lib\"",5140
%JAVA_OPTIONS%

Then I commented out our aspectJ agent and the startup was fine, the profiler was attached and the application seemed
started up fine. however, my application doesn't work correctly any more.

PS: In our webapp, we also uses spring 2.0.1 where some other AOP stuff is used as well.