Perhaps lines 656-658 are not working correctly with this FreeBSD setup?
#give the old response a dummy streamout- nasty hack, better idea
trans.response()._strmOut = ASStreamOut()
req._transaction = trans #this is needed by dispatchRequest
I'm not sure why the "old response" needs an instance of ASStreamOut.
On Wed, 2004-02-11 at 01:19, Ian Maurer wrote:
> Hello All,
> I have just recently ported my Webware application to a FreeBSD
> server and I am having some trouble with it that I cannot seem to
> figure out.
> Here is what I am using:
> FreeBSD 4.9-RELEASE #0
> mod_webkit adapter
> apache 1.3.28
> python 2.2.3
> The machine hosting me is either a VM or a chroot jail. I don't
> have access to raw sockets. Other than that, I don't have further
> details of the configuration but can ask my hoster if someone thinks
> the info might help solve the problem.
> What is happening:
> Basically Webware just stops accepting requests. The process is still
> running with the state of 'lockf' (important?) but it just doesn't
> Usually Webware just stops answering and the 'verbose' output
> shows the last request but no response is given:
> 363 2004-02-08 13:31:54 /WK/Context/Example
> (no 363 response)
> I am getting the following message at the end of the output LOG
> I am keeping:
> StreamOut Error: (54, 'Connection reset by peer')
> Which I believe comes from the ThreadedAppServer.py module at line
> I am really at a loss for where to start chasing down this problem.
> I have been running Webware for over 2 years without any problems,
> so I guess I am a little bit spoiled.
> Any thoughts or suggestions? Any more information needed?
> thanks in advance,
> Do you Yahoo!?
> Yahoo! Finance: Get your refund fast by filing online.
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> Webware-discuss mailing list