From: Edmund Lian <elian@in...> - 2003-03-05 23:28:59
Thanks for all your replies...
>Does the thread spin endlessly? This sounds like it _could_ be the same
>problem I ran into about a month ago, which had to do with concurrent
The thread actually works OK. I have it writing to the console at the start
of a run, and and the very end of a run. It also runs properly outside of
Webware. There are no error messages in any log.
What happens is that the task starts along with Webware, and runs fine. It
is run every 60 seconds, and during each run, it writes messages to the
console successfully. When I try to access any servlet through a browser
however, Webware stalls somewhere in the response cycle. since the browser
waits for returning data, but never gets any.
I've not been able to duplicate the problem today. Last night, it popped up
during 5 consecutive AppServer restarts. If Webware starts properly (i.e.,
the lock up does not occur), everything seems to be fine.
It could be related to the concurrent import problem since the problem
seems to be occuring at Webware start-up time only. I'm using Python 2.2.2,
so the patch that Jason mentions isn't on my system.
>To mitigate the problem in the meantime, I'd suggest adding
>from time import sleep
>to your periodic task (to delay its execution by a few seconds), and see
>if that helps.
I did this in the contextInitialize() function that kicks off the task, but
found that it just locks Webware up for the sleep period (why?). I'll try
moving the delay into the task itself to see if this still happens.
From: Jason Hildebrand <jason@pe...> - 2003-03-05 23:52:08
On Wed, 2003-03-05 at 17:28, Edmund Lian wrote:
> >To mitigate the problem in the meantime, I'd suggest adding
> >from time import sleep
> >to your periodic task (to delay its execution by a few seconds), and see
> >if that helps.
> I did this in the contextInitialize() function that kicks off the task, but
> found that it just locks Webware up for the sleep period (why?). I'll try
> moving the delay into the task itself to see if this still happens.
Yes, this is what I meant -- put the delay in the body of the task
Jason D. Hildebrand
Get latest updates about Open Source Projects, Conferences and News.