<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 28, 2020, at 7:34 PM, Levente Uzonyi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div><blockquote type="cite">A more specific/holistic evaluation of the server image after this fix:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">(Process allSubInstances select: [:ea | ea name includesSubstring: 'WebServer']) size " => 2 "<br></blockquote><br>Do you have 2 WebServer instances as well?<br></div></span></blockquote><div><br></div>No, just one. I previously destroyed the default instance via "WebServer reset". It is my understanding that the default instance is only used for testing and examples.</div><div><br></div><div>One of these two processes is this:</div><div><br></div><div>a Process in [] in DelayWaitTimeout>>wait</div><div>'WebServer''s listener process'</div><div><br></div><div>and the other is:</div><div><br></div><div>a Process in [] in BlockClosure>>newProcess</div><div>'[an IP address]:54090 - WebServer request handler'</div><div><br><div><br></div><blockquote type="cite"><div><blockquote type="cite"><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span>ifTrue: [ receiver outerContext receiver class == WebServer ]<br></blockquote><blockquote type="cite"><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-tab-span" style="white-space: pre; "> </span>ifFalse: [ false ] ] ] ] " size => 4"<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">WebServer allInstances first connections size " => 3"<br></blockquote><br>That should be 0 unless there are debuggers open or there are actual connections to your server.<br>Perhaps the Seaside error handler does something that doesn't let connections to be removed.<br></div></blockquote><br></div><div>Interesting, and very likely. I had indeed been doing some development which brought up the error handler perhaps three times.</div><div><br></div><div>If I do the following:</div><div><br></div><div>Utilities closeAllDebuggers. 3 timesRepeat: [Smalltalk garbageCollect].</div><div>WebServer allInstances first connections do: [:ea | PointerFinder on: ea]</div><div><br></div><div>Then all three look like this:</div><div><br></div><div><div>globals: Environment</div><div>declarations: IdentityDictionary</div><div>#WAServerManager -> WAServerManager class</div><div>default: WAValueHolder</div><div>contents: WAServerManager</div><div>adaptors: OrderedCollection</div><div>array: Array</div><div>1: WAWebServerAdaptor</div><div>server: WebServer</div><div>connections: IdentitySet</div><div>array: Array</div><div>494: Process</div><div><br></div><div>I tried using PointerFinder>>#on:except: to skip the WebServer's connections array, but it did not seem to skip the connections array. :)</div><div><br></div><div>Could some of my problem been due to my having inspected WebServer's connections collection without acquiring a mutex? I see mention of this in a comment in WebServer>>#connections ... but I also don't see any methods in WebServer which seem to support safe public access to the collection, so perhaps that remains TBD.</div><div><br></div><div>In any case, I have done the following:</div><div><br></div><div>WebServer allInstances first destroyConnections</div><div><br></div><div>And all of the stale connections are gone. :) I still have the extra (second) request handler process hanging out though.</div><div><br></div><div>Thanks,</div><div>a Tim</div><div><br></div></div><div><br></div></body></html>