Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » StuckThreadMaxTime in weblogic
StuckThreadMaxTime in weblogic [message #842702] Thu, 12 April 2012 14:46 Go to next message
Kris Lind is currently offline Kris Lind
Messages: 2
Registered: April 2012
Junior Member
EclipseLink 2.1.0 ( also tried 2.1.3 )
Weblogic 10.3.0.0

I am getting some StuckThreadMaxTime in my weblogic server. I can see that it ends in some eclipselink classes. See stacktrace...

It happens randomly when we stress the system.

There is no locks in the database and it performs good.


<Apr 12, 2012 3:49:32 PM CEST> <Error> <WebLogicServer> <BEA-000337> <[STUCK] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "623" seconds working on the request "dk.steria.skat.ics.risikoinformation.session.facade.RisFacadeSBBean_e5e3k_RisFacadeSBBeanRemoteImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
java.lang.Thread.sleep(Native Method)
java.lang.Thread.sleep(Thread.java:851)
org.eclipse.persistence.internal.helper.ConcurrencyManager.releaseDeferredLock(ConcurrencyManager.java:464)
org.eclipse.persistence.internal.identitymaps.CacheKey.releaseDeferredLock(CacheKey.java:348)
org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:838)

[Updated on: Thu, 12 April 2012 14:47]

Report message to a moderator

Re: StuckThreadMaxTime in weblogic [message #846664 is a reply to message #842702] Mon, 16 April 2012 14:57 Go to previous messageGo to next message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

Seems to be a cache deadlock.

See,
http://wiki.eclipse.org/EclipseLink/FAQ/JPA#How_to_diagnose_and_resolve_hangs_and_deadlocks.3F

Normally for a deadlock you need at least two different threads competing for the same resources. Are there other blocked threads?

From the stack there are several session beans on the stack, are they using the same transaction/persistence context, or are you using different transactions that could be locking on each other?



James : Wiki : Book : Blog : Twitter
Re: StuckThreadMaxTime in weblogic [message #847366 is a reply to message #846664] Tue, 17 April 2012 08:26 Go to previous messageGo to next message
Kris Lind is currently offline Kris Lind
Messages: 2
Registered: April 2012
Junior Member
I disabled the shared cache, and that seems to work.
<property name="eclipselink.cache.shared.default" value="false"/>

I am using a IBM JVM -
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460sr9fp1-20110208_03(SR9 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110203_74623 (JIT enabled, AOT enabled)
J9VM - 20110203_074623
JIT - r9_20101028_17488ifx3
GC - 20101027_AA)
JCL - 20110203_01

Dont know if that could be a problem

Re: StuckThreadMaxTime in weblogic [message #849394 is a reply to message #847366] Thu, 19 April 2012 05:30 Go to previous messageGo to next message
klind Mising name is currently offline klind Mising name
Messages: 5
Registered: August 2011
Junior Member
I found this one :
bugs.eclipse.org/bugs/show_bug.cgi?id=321473
and tried to use 2.2.0, but I still get the same error.
I also tried running my load test on my windows with 2.1.0 and 2.2.0, and there was no problem here.
So I guess it has something to do with AIX and IBM jvm.
Re: StuckThreadMaxTime in weblogic [message #849855 is a reply to message #849394] Thu, 19 April 2012 14:00 Go to previous messageGo to next message
James Sutherland is currently offline James Sutherland
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

It could just be a timing issue, in that the AIX system is running faster or with more concurrency (or possibly less too).

If you can create something reproducible, please log a bug. Also try the latest 2.3 release.


James : Wiki : Book : Blog : Twitter
Re: StuckThreadMaxTime in weblogic [message #1022445 is a reply to message #842702] Thu, 21 March 2013 22:30 Go to previous message
jsh jsh is currently offline jsh jsh
Messages: 1
Registered: March 2013
Junior Member
We ran into a similar issue as many threads go into indefinite wait because of an unending while loop (see stack-trace). Inside releaseDeferredLock function, there is a weird logic where an unending while loop invokes a recursive function:-(

&quot;http-thread-pool-8181-(1)&quot; daemon prio=10 tid=0x00007f4ccc039000 nid=0x13b3 sleeping[0x00007f4caf4ef000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
    at java.lang.Thread.sleep(Native Method)
    at org.eclipse.persistence.internal.helper.ConcurrencyManager.releaseDeferredLock(ConcurrencyManager.java:464)
    at org.eclipse.persistence.internal.identitymaps.CacheKey.releaseDeferredLock(CacheKey.java:379)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:759)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildWorkingCopyCloneNormally(ObjectBuilder.java:619)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObjectInUnitOfWork(ObjectBuilder.java:572)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:504)
    at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:463)
    at org.eclipse.persistence.queries.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:723)
    at org.eclipse.persistence.queries.ReadAllQuery.registerResultInUnitOfWork(ReadAllQuery.java:742)


We are using 2.2.1 on UBUNTU 12.04 running jdk1.6.0_41

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 20.1-b02 (Sun Microsystems Inc.)
Specification-Title: Eclipse Persistence Services
Specification-Vendor: Eclipse.org - EclipseLink Project
Specification-Version: 2.2.1
Implementation-Title: org.eclipse.persistence
Implementation-Vendor: Eclipse.org - EclipseLink Project
Implementation-Version: 2.2.1.v20110722-r9776
Release-Designation: EclipseLink 2.2.1
Premain-Class: org.eclipse.persistence.internal.jpa.deployment.JavaSEC
MPInitializerAgent
Main-Class: org.eclipse.persistence.Version
Previous Topic:JPA-RS: @OneToOne relationship problem
Next Topic:@XmlInverseReference back pointer not set on unmarshalling
Goto Forum:
  


Current Time: Thu Oct 30 13:12:10 GMT 2014

Powered by FUDForum. Page generated in 0.01971 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software