Re: Lifebeat
Re: Lifebeat
- Subject: Re: Lifebeat
- From: Chuck Hill <email@hidden>
- Date: Tue, 4 Mar 2008 12:57:33 -0800
On Mar 4, 2008, at 12:06 PM, Robert Walker wrote:
The lifebeat has nothing to do with your long running response
problem.
Hold on there, Valerio said:
the application still shuts down if it takes more than 30 seconds
That is wotaskd killing an unresponsive app, IIRC. The adaptor
timeouts should not affect this. I thought that the lifebeat came
through on a different request handler, but if it gets blocked by
having concurrent request handling off, that could explain this.
Valerio: WOLifebeatInterval controls how often the app is checked, not
how long wotaskd waits for a response.
I think we need more information: which version of WO, is concurrent
request handling on or off, what do you see in the app log when it
shuts down? Is the app running out of memory?
Chuck
There are adaptor settings to adjust the send and receive timeouts.
That being said, I am in complete agreement with Miguel. Adjusting
the timeouts is not the best way to solve the long response issues.
If your response takes more than a few seconds your users will
assume something is wrong and will either start clicking on things,
click their bookmark to get back to the sign-in page, or simply
close the browser window.
I you need to use a long running response, you need a way to inform
your users that something is happening. A progress bar is nice, but
if not possible, you need at least something to indicate that
something is happening. The long response page is one way to do
this, but an even better way could be to use an asynchronous AJAX
request. In either case run the long processing in a separate thread
as previously suggested.
On Mar 4, 2008, at 2:22 PM, Miguel Arroz wrote:
Hi!
You are trying to solve the problem in the wrong way. If you have
a long operation, you should do it on a separate thread, and use
WOLongResponse or the Ajax similar to handle the user interface.
That way, you won't have any problem with lifebeat.
Yours
Miguel Arroz
On 2008/03/04, at 19:16, Valerio Luccio wrote:
Hello,
I have a WebObject application running on a Mac. Recently some
operations have taken more than 30 seconds, which forces the
application to restart. I've increased the lifebeat value to 60
through WOMonitor and when I look at how the process was launched,
sure enough, I see "-WOLifebeatInterval 60", yet the application
still shuts down if it takes more than 30 seconds. Why is that ?
How can I get this guy to behave the way I want ?
Thanks,
--
Valerio Luccio (212) 998-8736
Center for Brain Imaging 4 Washington Place, Room 156
New York University New York, NY 10003
"In an open world, who needs windows or gates?"
_______________________________________________
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
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
_______________________________________________
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
Robert Walker
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:
This email sent to email@hidden
--
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
| References: | |
| | >Lifebeat (From: Valerio Luccio <email@hidden>) |
| | >Re: Lifebeat (From: Miguel Arroz <email@hidden>) |
| | >Re: Lifebeat (From: Robert Walker <email@hidden>) |