[Seaside] Re: Connection Closed failure - should something handle
arning at charm.net
Fri Aug 20 10:00:39 UTC 2010
FWIW, this happens in non-Pharo Squeak as well. Sometimes 3 or 4 in
On 8/20/10 3:47 AM, Lukas Renggli wrote:
> Hi Tim,
> This could be due to a change in the Sockets in Pharo, that's maybe
> why other people do not see it. It is definitely a bug to get
> I don't have time to investigate further right now, but I guess
> somebody will come up with a fix quickly :-)
> On 20 August 2010 09:44, Nick Ager<nick.ager at gmail.com> wrote:
>> Hi Tim,
>>> Still - it would seem that by signalling this - it could happen, and
>>> something should catch it?
>>> Looking again, I see the following method in the stack:
>>> WAListenerAdaptor>>waitForConnection: aSocket
>>> | socket stream |
>>> socket := aSocket waitForAcceptFor: 10.
>>> socket isNil ifTrue: [ ^ self ].
>>> stream := SocketStream on: socket.
>>> [ [ [ self process: stream ]
>>> ensure: [ stream close ] ]
>>> ifCurtailed: [ socket destroy ] ]
>>> forkAt: Processor userBackgroundPriority
>>> Shouldn't that ifCurtailed: prevent this walkback?
>> It doesn't prevent the walkback, but makes sure that "socket destroy" is
>> called. Experiment with:
>> [Error signal] ifCurtailed: [Transcript show: 'Abandoned'; cr].
>> Transcript show: 'Proceeded'; cr
>> from the excellent exception PBE draft
>> chapter: https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.pdf
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside