My Oracle Support Banner

WLS 10.3.2: Stuck Threads From AjTypeSystem Class of AspectJ Framework During Stress Testing (Doc ID 1147663.1)

Last updated on APRIL 06, 2018

Applies to:

Oracle WebLogic Server - Version 10.3.2 to 10.3.3
Information in this document applies to any platform.

Symptoms

While doing stress test on Spring and Oracle ADF application deployed in WLS 10.3.2, below struck threads are seen related to AspectJ Framework libraries.

"[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" id=14 idx=0x40 tid=6636 prio=1 alive, daemon
at java/util/WeakHashMap.getEntry(WeakHashMap.java:382)
at java/util/WeakHashMap.containsKey(WeakHashMap.java:369)
at com/bea/core/repackaged/aspectj/lang/reflect/AjTypeSystem.getAjType(AjTypeSystem.java:37)
at com/bea/core/repackaged/springframework/aop/aspectj/annotation/AbstractAspectJAdvisorFactory.isAspect(AbstractAspectJAdvisorFactory.java:120)
at com/bea/core/repackaged/springframework/aop/aspectj/annotation/BeanFactoryAspectJAdvisorsBuilder.buildAspectJAdvisors(BeanFactoryAspectJAdvisorsBuilder.java:104)
^-- Holding lock:
com/bea/core/repackaged/springframework/aop/aspectj/annotation/BeanFactoryAspectJAdvisorsBuilder@0x5e15e388[thin lock]
at com/bea/core/repackaged/springframework/jee/intercept/InterceptionMetadata.addAspectJAdvisors(InterceptionMetadata.java:813)
at com/bea/core/repackaged/springframework/jee/intercept/InterceptionMetadata.createProxyIfNecessary(InterceptionMetadata.java:465)
at com/bea/core/repackaged/springframework/jee/intercept/InterceptionMetadata.createProxyIfNecessary(InterceptionMetadata.java:401)
at com/bea/core/repackaged/springframework/jee/spi/EjbComponentCreatorBrokerImpl.invokeCreateProxyIfNecessary(EjbComponentCreatorBrokerImpl.java:118)
at com/bea/core/repackaged/springframework/jee/spi/EjbComponentCreatorBrokerImpl.getBean(EjbComponentCreatorBrokerImpl.java:75)
at weblogic/ejb/container/injection/EjbComponentCreatorImpl.getBean(EjbComponentCreatorImpl.java:68)
at weblogic/ejb/container/manager/BaseEJBManager.createNewBeanInstance(BaseEJBManager.java:216)
at weblogic/ejb/container/manager/BaseEJBManager.allocateBean(BaseEJBManager.java:233)
at weblogic/ejb/container/manager/MessageDrivenManager.createBean(MessageDrivenManager.java:291)
at weblogic/ejb/container/pool/MessageDrivenPool.createBean(MessageDrivenPool.java:174)
at weblogic/ejb/container/pool/MessageDrivenPool.getBean(MessageDrivenPool.java:

Changes

None.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.