• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • Sessions
  • hhuynh
  • Reporter: amiller
  • September 14, 2007
  • 0
  • Watchers: 0
  • September 25, 2007
  • September 14, 2007

Description

As a result of Weblogic 9 changes in 2.4.3, Weblogic 8 prints this error in the terracotta-client.log file. WL8 still works fine, this just looks scary - it’s basically trying to weave a class that doesn’t exist in WL8. This is reproducible with pretty much any WL8 container test.

2007-09-14 12:31:44,932 [main] ERROR com.terracottatech.dso.instrumentation - Aspect module [com.tc.weblogic.SessionAspectModule] could not be deployed in [email protected]; com.tc.aspectwerkz.exception.DefinitionException: could not find advice method [addFilterIfNeeded(StaticJoinPoint jp, weblogic.servlet.internal.FilterManager filterManager)] in [com.tc.weblogic.SessionAspectWL9] (are you using a compiler extension that you have not registered?) (are you using XML defined advice, with StaticJoinPoint bindings without specifying the fullsource like signature?) com.tc.aspectwerkz.exception.DefinitionException: could not find advice method [addFilterIfNeeded(StaticJoinPoint jp, weblogic.servlet.internal.FilterManager filterManager)] in [com.tc.weblogic.SessionAspectWL9] (are you using a compiler extension that you have not registered?) (are you using XML defined advice, with StaticJoinPoint bindings without specifying the fullsource like signature?) at com.tc.aspectwerkz.definition.DefinitionParserHelper.createMethodInfoForAdviceFQN(DefinitionParserHelper.java:479) at com.tc.aspectwerkz.definition.deployer.AspectDefinitionBuilder.addAdvice(AspectDefinitionBuilder.java:67) at com.tc.weblogic.SessionAspectModule.addWL9Aspect(SessionAspectModule.java:42) at com.tc.weblogic.SessionAspectModule.deploy(SessionAspectModule.java:16) at com.tc.aspectwerkz.definition.deployer.StandardAspectModuleDeployer.loadModule(StandardAspectModuleDeployer.java:140) at com.tc.aspectwerkz.definition.deployer.StandardAspectModuleDeployer.doDeploy(StandardAspectModuleDeployer.java:131) at com.tc.aspectwerkz.definition.deployer.StandardAspectModuleDeployer.deploy(StandardAspectModuleDeployer.java:67) at com.tc.object.bytecode.hook.impl.DefaultWeavingStrategy.transform(DefaultWeavingStrategy.java:104) at com.tc.object.bytecode.hook.impl.DSOContextImpl.preProcess(DSOContextImpl.java:138) at com.tc.object.bytecode.hook.impl.ClassProcessorHelper.defineClass0Pre(ClassProcessorHelper.java:517) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at weblogic.socket.JVMSocketManager.(JVMSocketManager.java:70) at weblogic.t3.srvr.T3Srvr.setJVMID(T3Srvr.java:637) at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:790) at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343) at weblogic.Server.\_\_tc\_main(Server.java:32) at weblogic.Server.main(Server.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.tc.test.server.appserver.cargo.CargoLinkedChildProcess.main(CargoLinkedChildProcess.java:52)

Comments

Alex Miller 2007-09-14

Added check to determine whether Weblogic 8 or 9 is being used and to weave the appropriate aspect. Before both aspects were being woven and the WL 9 aspect would fail on WL 8 as the class did not exist.

Tested some container tests on both WL 8 and WL 9, verified tests still pass and exception is no longer present in the log. Applied fix to trunk with 5598 and to the 2.4 branch (post 2.4.3 release) as 5599. Any 2.4.x after 2.4.3 should contain the fix.