[BUG] Server crashes after 1st request (was Re: [Pangloss] Dependencies and running the test server)

[Steve Purkis]

On Mar 4, 2004, at 22:49, Steve Purkis wrote:

> On Wednesday, March 3, 2004, at 01:26  pm, Bruno Postle wrote:
>
>> On Tue 02-Mar-2004 at 10:39:18PM +0000, Steve Purkis wrote:
>>> On Friday, February 27, 2004, at 02:10  pm, Bruno Postle wrote:
>>> (8929) serving request for /pcie.css
>>> [Pipeline::Dispatch] dispatching to OpenFrame::Segment::HTTP::Request
>>> [Pipeline::Dispatch] dispatching to Pangloss::Segment::StoreRequest
>>> [Pangloss::Segment::StoreRequest] saving copy of original request
>>> [Pipeline::Dispatch] dispatching to  
>>> OpenFrame::WebApp::Segment::Session::CookieLoader
>>> [Pipeline::Dispatch] dispatching to Pipeline
>>> [Pipeline::Dispatch] dispatching to  
>>> OpenFrame::WebApp::Segment::Decline::StaticContent
>>> [Pipeline::Dispatch] dispatching to  
>>> OpenFrame::Segment::HTTP::Response
>>> [OpenFrame::Segment::HTTP::Response::OpenFrame::Segment::HTTP:: 
>>> Response::dispatch] no response available at  
>>> /usr/lib/perl5/site_perl/5.8.1/Pipeline/Dispatch.pm line 74
>>> [Pipeline::Dispatch] dispatching to  
>>> OpenFrame::WebApp::Segment::Session::Saver
>>> [Pangloss::WebApp::Standalone::handle_request] sent response (122  
>>> characters)
>>
>> Note that actually the server crashed serving the /pcie.css request.

[snip!]

>> Basically, the server crashes after the first request, I can now
>> access other Pangloss paths such as /login.html by restarting the
>> server before making the request.

Well, it looks like this bug is due to some of the changes that have  
been made to the Pipeline module over the past year.  I don't know  
exactly what's causing it yet, but I do know that down-grading to  
Pipeline-3.06 fixes the problem (running standalone server, perl 5.8.4  
on OS X, haven't tried it with Apache yet).

So in the interests of getting this up & running, I'd suggest  
downgrading Pipeline on your production server (unless another package  
you're using relies on a more recent version).  Once this bug is fixed  
you'll be able to upgrade again.

Cheers,
+--
   Steve Purkis      |      www.quiup.com      |      Quiup Ltd.