Hi, because of [1] I use ThreadPool [2] and while developing on my mac it worked fine. But now, testing it on my production server which is a windows machine, it does not work which means, it is some kind of magic, the code within the block [anObject doSomething] queueWork is not run. When changing it to [anObject halt doSomething] queueWork the code is run! Changing my code from >>queueWork back to >>fork proves that everything is fine now and there is a problem with ThreadPool. When I was playing around to find the problem, I noticed the following: I created a button like this: html mdlButton onClick: (html jQuery ajax script: [ :script | | theSession | theSession := self session. [ theSession inspect ] queueWork. ]); with: 'test' Mac: it works nearly immediately Windows: it does not work ... except when I add a halt in it but: When I then do this after clicking on the test button: 20 timesRepeat: [[ Transcript crShow: Time now printString] queueWork ], the sessions inspector also comes up It seems that the process is hanging until the next work is to be done. Before going deeper in it my question is: does anyone use it on windows? is it made for windows, too? are there any experiences with windows and ThreadPool? did I miss something? how can I fix this? Regards Sabine [1] http://forum.world.st/ThreadPool-with-Seaside-how-td4956812.html#a4957192 [2] http://smalltalkhub.com/#!/~pdebruic/ThreadPool/