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: Marcos Trejo Munguia <email@hidden>
- Date: Thu, 10 Nov 2005 10:43:54 -0600
Hello Lindesay:
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?
A) I'm using my own editing contexts, and I'm locking them in
WOComponent's awake method and unlocking them in WOComponent's sleep
method
B) I'm only use the default editing context to read never to write, and
I'm not locking this editing context.
C) I'm not sure, Do I have to see a java.lang.OutOfMemoryError to know
for sure that I'm running out of memory? If the answer is yes then I'm
not having this problem, if is not then how do I know that I'm running
out of memory?
Thank you for your answer.
_______________________________________________
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