<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Here's a couple posts from before.<div><br></div><div>http://lists.squeakfoundation.org/pipermail/seaside/2010-July/023793.html</div><div><br></div><div>I still have this problem regularly... I wanna say Announcements have something to do with it as well? Or maybe it's just by virtue of refreshing.</div><div><br></div><div>RS<br><br><hr id="stopSpelling">Date: Fri, 20 Aug 2010 06:00:39 -0400<br>From: arning@charm.net<br>To: seaside@lists.squeakfoundation.org<br>Subject: Re: [Seaside] Re: Connection Closed failure - should something handle this?<br><br>
<meta http-equiv="Content-Type" content="text/html; charset=unicode">
<meta name="Generator" content="Microsoft SafeHTML">
<font face="Georgia">FWIW, this happens in non-Pharo Squeak as well.
Sometimes 3 or 4 in rapid succession.<br>
<br>
Cheers,<br>
Bob<br>
</font><br>
On 8/20/10 3:47 AM, Lukas Renggli wrote:
<blockquote cite="mid:AANLkTinaxViYh_KyDKikJ99Tcgd-k=XH-=OSeq_mKMYU@mail.gmail.com">
<pre>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
debuggers.
I don't have time to investigate further right now, but I guess
somebody will come up with a fix quickly :-)
Lukas
On 20 August 2010 09:44, Nick Ager <a class="ecxmoz-txt-link-rfc2396E" href="mailto:nick.ager@gmail.com"><nick.ager@gmail.com></a> wrote:
</pre>
<blockquote>
<pre>Hi Tim,
</pre>
<blockquote>
<pre>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?
</pre>
</blockquote>
<pre>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: <a class="ecxmoz-txt-link-freetext" href="https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.pdf" target="_blank">https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.pdf</a>
Nick
_______________________________________________
seaside mailing list
<a class="ecxmoz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>
<a class="ecxmoz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
</blockquote>
<pre>
</pre>
</blockquote>
<br>_______________________________________________
seaside mailing list
seaside@lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</div> </body>
</html>