RE: Help with stack trace from frozen application
RE: Help with stack trace from frozen application
- Subject: RE: Help with stack trace from frozen application
- From: email@hidden
- Date: Thu, 10 Nov 2005 14:40:22 +1300
Hello Marcos;
Attempting to answer a question like this is a bit of a tricky thing
as the issue could be caused by a number of things. I suppose some
useful things to first check...
A) If you are creating your own editing contexts, are you locking and
unlocking them appropriately?
B) Are you manually locking a "default editing context" from the
session? (if so, why?)
C) Could you be running out of memory handling a request?
cheers.
[3] com.webobjects.foundation.NSRecursiveLock.lock
(NSRecursiveLock.java:72)
[4] com.webobjects.eocontrol.EOEditingContext.lock
(EOEditingContext.java:4,624)
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
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