A WOLongResponsePage that _sometimes_ seems to create a deadlock
A WOLongResponsePage that _sometimes_ seems to create a deadlock
- Subject: A WOLongResponsePage that _sometimes_ seems to create a deadlock
- From: Kaj Hejer <email@hidden>
- Date: Wed, 4 May 2005 14:39:37 +0200
Hi!
We have a WOLongResponsePage that _sometimes_ seems to create a
deadlock. What we observe is that the applications isn't answering to
requests. It is not so easy to reproduce. I have just managed to
reproduce this once in testing. I created a thread dump with kill
-QUIT.
Can the use of a inner class create any problems, ref. the followings
lines that refere to the constructor of our inner class (Rapport1 is
out WOLongResponsePage and SvaraltLight is a inner class, see the url
to the sourcefile bellow):
at
com.webobjects.eocontrol._EOCheapCopyMutableArray.count(_EOCheapCopyMuta
bleArray.java:92)
at Sporsmal.getSvaralternativCount(Sporsmal.java:237)
at Rapport1$SvaraltLight.<init>(Rapport1.java:59)
Are the following lines interesting since they include NSRecursiveLock:
"WorkerThread7" prio=5 tid=0x00477840 nid=0x13 in Object.wait()
[f0100000..f01019c8]
at java.lang.Object.wait(Native Method)
- waiting on <0xf411e370> (a
com.webobjects.foundation.NSRecursiveLock)
at java.lang.Object.wait(Object.java:429)
at
com.webobjects.foundation.NSRecursiveLock.lock(NSRecursiveLock.java:72)
- locked <0xf411e370> (a
com.webobjects.foundation.NSRecursiveLock)
at
com.webobjects.eocontrol.EOEditingContext.lock(EOEditingContext.java:
4607)
at Rapport1.awake(Rapport1.java:103)
at
com.webobjects.appserver.WOComponent._awakeInContext(WOComponent.java:
862)
at
com.webobjects.appserver.WOSession.restorePageForContextID(WOSession.jav
a:710)
at
com.webobjects.appserver._private.WOComponentRequestHandler._restorePage
ForContextID(WOComponentRequestHandler.java:156)
Should this be something to worry about or should I look elsewhere to
solve this issue?
We create our own EOObjectStoreCoordinator to not block the rest of the
app from serving requests:
EOObjectStoreCoordinator osc = new EOObjectStoreCoordinator();
//editingContext = new LockErrorScreamerEditingContext(osc);
editingContext = new EOEditingContext(osc);
getSession().writeLog("Rapport1:constructor:EOObjectStoreCoordinator: "
+ osc);
getSession().writeLog("Rapport1:constructor:editingContext: " +
editingContext);
editingContext.setSharedEditingContext(null);
The sourcecode for this page can be found at
http://folk.uio.no/kajh/tmp/Rapport1.java
The full thread dump can be found at
http://folk.uio.no/kajh/tmp/dump.txt
We are using WO5.2.3, solaris and Oracle 9.2.
TIA for any input on this issue! :)
-Kaj :)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden