AnsweredAssumed Answered

Weblogic stucked by lisa class AbstractHashedMap ?

Question asked by Benoit_B on Mar 15, 2017
Latest reply on Jun 21, 2017 by Benoit_B

Hello Everybody,

 

We are making a benchmark on weblogic server using virtual services.

Sometimes, the following error occurs : 

[DevTest AGENT:A][WARN][6548][37][Stats Gathering Thread][03/13 16:36:26 (748)] Message Flooding [Total:731][[AgentInfo:1][[Connection:717][[Queue:0][[Stats:1][[Transaction:0][[Ticket:0][[UI:0][[VSE:12][[Invocation:0]
[DevTest AGENT:A][WARN][6548][354][[ACTIVE] ExecuteThread: '199' for queue: 'weblogic.kernel.Default (self-tuning)'][03/13 16:36:26 (996)] VSE supplied a no hijack directive. This may or may not be expected. Falling back on live system...
<Mar 13, 2017 4:36:27 PM CET> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "617" seconds working on the request "Workmanager: default, Version: 0, Scheduled=true, Started=true, Started time: 617288 ms
", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:
com.itko.lisa.remote.utils.AbstractHashedMap.put(ReferenceMap.java:1424)
com.itko.lisa.remote.utils.AbstractReferenceMap.put(ReferenceMap.java:356)
com.itko.lisa.remote.utils.ReferenceMap.put(ReferenceMap.java:74)
com.itko.lisa.remote.utils.IdentityWeakReferenceMap.put(IdentityWeakReferenceMap.java:74)
com.itko.lisa.remote.instrument.InstanceTracker.track(InstanceTracker.java:280)
weblogic.servlet.internal.session.SessionData.<init>(SessionData.java:124)
weblogic.servlet.internal.session.SessionData.<init>(SessionData.java:127)
weblogic.servlet.internal.session.MemorySessionData.<init>(MemorySessionData.java:9)
weblogic.servlet.internal.session.MemorySessionContext.getNewSession(MemorySessionContext.java:21)

 

Any ideas ? 

 

Regards,

 

Benoit

Outcomes