Ian Maurer wrote:
> --- Geoffrey Talvola <[EMAIL PROTECTED]> wrote:
>> deelan wrote:
>>> Geoffrey Talvola wrote:
>>>
>>>> Are you using the latest version of mod_webkit from CVS? There have
>>>> been bugfixes since Webware 0.8.1, and it's possible the bugs could
>>>> cause lockups or crashes.
>>>
>>> no, i'm using apache 1.3 + mod_webkit from webware 0.8.1.
>>> from what i see mod_webkit for apache 1.3 (unlike
>>> mod_webkit2) has not be patched recently:
>>>
>>> <http://cvs.sourceforge.net/viewcvs.py/webware/Webware/WebKit/
>>> Adapters/>
>>
>> You're right, I forgot that the bugfixes were only for Apache 2.0.
>>
>>> if you suspect that lockups could be caused by python
>>> code other than C code in mod_webkit i could try to update my
>>> webware to CVS version, but i'm a bit reclutant to do that since
>>> i've got some production code running with 0.8.1.
>>
>> I don't know of anything in the Python code in 0.8.1 that would cause
>> lockups -- sorry.
>>
>> - Geoff
>
> I am just reporting that I have had the same issue on my laptop which
>
> is very low-powered:
>
> - RedHat 8
> - 267 MHZ Pentium II - Dell Latitude
> - Webware 0.8.1
> - Apache 1.3
> - mod_webkit
>
> The app server starts up fine but eventually it will end up just
> sitting there not even showing any requests coming in. To get things
> working again I would not only have to restart the appserver but
> apache as well. This leads me to believe it may be a mod_webkit issue
> but I am not sure.
>
> I normally don't use this laptop for anything other than an X client
> to my desktop server, but I tried setting up the laptop for a travel
> and I wasn't able to get past this issue.
It would be good to determine if individual threads in the thread pool are
getting locked up, which would eventually reduce your threads from its
initial pool of 10 threads (or whatever) to 0 threads -- at that point the
application will be locked up. I would recommend placing a call like this:
print '***** starting request on thread',
threading.currentThread().getName()
at the beginning of RequestHandler.handleRequest in ThreadedAppServer.py,
and
print '***** done with request on thread',
threading.currentThread().getName()
at the end of that method. Then you will be able to examine your logfile to
see if threads are getting wedged in the middle of a request.
- Geoff
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss