[Seaside] Re: Error: invalid http status line
andreas.raab at gmx.de
Thu Sep 23 16:59:37 UTC 2010
Try removing the original adapter. A while ago I had a similar problem
which I tracked to some odd logic that would disallow starting any
adapters if there was more than one present (not running!) for a single
port. I.e., if I remember correctly, launching Seaside, stopping the
initial adapter, and adding another adapter at 8080 would cause neither
of them to start. Took me some time to figure out that I hadn't broken
Seaside with my adapter but rather that it was the server manager which
implemented this (rather odd) policy.
On 9/23/2010 9:42 AM, Rob Withers wrote:
> Ok, I downloaded the one-click Seaside 3.0 image and ran it. I stopped
> the Comanche adapter and added an adapter for WAListenerAdapter on 8080.
> I am unable to start it.
> From: "Torsten Bergmann" <astares at gmx.de>
> Sent: Thursday, September 23, 2010 11:25 AM
> To: <seaside at lists.squeakfoundation.org>
> Subject: [Seaside] Error: invalid http status line
>> Hi Rob,
>>> It originally happened in an image I had built from 4.1 by loading
>>> all Trunk
>>> versions up to current. I just took a Squeak4.2-10382 image, loaded
>>> by running:
>> Is this reproducable in Pharo too? Seaside uses Pharo as development
>> platform, so I would try there first. So you could find out if it
>> is a real Seaside bug or a Squeak/Pharo compatibility issue.
>> Although there is a prebuilt Seaside image available in the
>> download section of squeak.org (based on Squeak 4.1.) I dont
>> know if there is some official Squeak maintainer for a Squeak
>> Seaside port...
>> The best would be to try the prebuilt Seaside image provided at
>> Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
>> Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
More information about the seaside