Oh boy, I really started something ! :) I was hoping to get an answer
like set this variable ..., instead I got a very interesting dissertation.
Anyway, solving my problem is not that important, since it's such a rare
occurrence, but all the answers made me learn a lot and pointed me to
other
On Mar 5, 2008, at 8:05 AM, Valerio Luccio wrote:
Oh boy, I really started something ! :) I was hoping to get an
answer like set this variable ..., instead I got a very
interesting dissertation.
Anyway, solving my problem is not that important, since it's such a
rare occurrence, but all
Le 08-03-05 à 12:35, Chuck Hill a écrit :
On Mar 5, 2008, at 8:05 AM, Valerio Luccio wrote:
Oh boy, I really started something ! :) I was hoping to get an
answer like set this variable ..., instead I got a very
interesting dissertation.
Anyway, solving my problem is not that important,
On Mar 5, 2008, at 10:44 AM, Miguel Arroz wrote:
Hi!
Yes, I'm living almost on the California time zone, despite the
fact that I live in a GMT country... :) Anyway, I go to sleep late
but I also wake up late. I really wish I could handle sleeping less
time per day like the Wonder boys,
Hi!
Yes, I'm living almost on the California time zone, despite the
fact that I live in a GMT country... :) Anyway, I go to sleep late but
I also wake up late. I really wish I could handle sleeping less time
per day like the Wonder boys, but unfortunately, I can't... :(
Oh, and about
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
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
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
The lifebeat has nothing to do with your long running response problem.
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
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
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
control that ?
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
or the Ajax similar to handle the user
interface. That way, you won't have any problem with lifebeat.
Of course you're right Miguel, but this is an exceptional case,
that operation usually takes between 1 and 4 seconds and I didn't
think it was worth separate threads. I don't feel like making
not fix
this problem. Would that be correct? Same would go for concurrent
request handling right?
I am not 100% sure. The WOLongResponse page would free up the request
dispatch loop which should result in the lifebeat getting sent. I
think it is the stall in the RR loop that is causing
WOLongResponse or the Ajax similar to handle the user interface.
That way, you won't have any problem with lifebeat.
Of course you're right Miguel, but this is an exceptional case, that
operation usually takes between 1 and 4 seconds and I didn't think
it was worth separate threads. I don't
that at
least something is happening and that the app probably isn't hung.
Same would go for concurrent request handling right?
Right, unless the app has multiple EOF stacks.
The WOLongResponse page would free up the request dispatch loop
which should result in the lifebeat getting
loop
which should result in the lifebeat getting sent.
I'm pretty certain that I have seen a lifebeat thread in WO app
thread dumps. If so, blockage in the request dispatch loop
shouldn't affect the timely sending of the lifebeat.
The documentation says:
If the application
17 matches
Mail list logo
