Re: WO application silently dies.
Re: WO application silently dies.
- Subject: Re: WO application silently dies.
- From: Chuck Hill <email@hidden>
- Date: Mon, 24 Oct 2005 10:31:11 -0700
On Oct 24, 2005, at 8:06 AM, Gennady Kushnir wrote:
More details:
After more precious debugging I've found out that application stops
operating at restoreSessionWithID step.
When I click link in already frozen window debugger comes up to
handlerForRequest and also stops.
That most likely means that the previous request for that session did
not check the session back in. Do you have a sleep() method in
Session? If so, make sure that it can never throw an exception.
Another possibility is that you have left a lock on
session.defaultEditingContext() from the last request. This will
also result in the behavior you are describing, but I am not sure if
this happens in restoreSessionWithID or a little later and I am too
lazy to look it up. :-)
A final possibility is that in Session.awake() you are blocking on
something the previous request did not release / unlock.
Can it be concerned with memory?
Probably not.
It freezes when I try to work with "virtual" objects that are not
saved into database yet. When I perform the same task on objects in
database - there is no problem.
I have from about 20 to over 100 interconnected EOs displayed on
one page and stored temporarily in editingContext created
especially for them : child of session().defaultEdtingContext().
Check how you have handled the locking of this EC you have created
(see above for why). It sounds like you might be locking it and
leaving it locked when the response is returned.
Chuck
On 24.10.2005, at 14:49, Gennady Kushnir wrote:
Hello, list.
After making some minor modifications to my applications business
logic i've bumped into strange bug.
When I click try to perform some certain actions Safari writes
"connecting to server: 127.0.0.1" and after that application does
not respond to any requests. There are no error messages in system
out.
I can separate these "certain actions" from others as "leading to
addition of new EOs".
I tried to debug the problem. But but debugger doesn't come to the
breakpoint in the action invoked by these buttons, and even to
Component's invokeAction and Application's takeValuesFromRequest.
However some lower layer still lives. I say that because when I
click some links many times there appears in output console:
[2005-10-24 14:43:09 MSD] <WorkerThread15>
<com.webobjects.appserver._private.WODefaultAdaptor>: Growing
number of WOWorkerThreads to 32
However still nothing is returned and debugger does not come to
any breakpoint.
Where may be the problem?
Thanks in advance
Gennady
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
408ka.mipt.ru
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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