Comanche - Failed primitives in Socket objects

Kamil Kukura kamk at volny.cz
Tue Jul 13 08:43:14 UTC 2004


Frantisek Fuka wrote:
> While running the latest Comanche on Windows 98 and setting mode: to
> #debug, I get lots of "Failed primitive" exceptions in Socket objects
> almost immediately when I try a simple "load test" (holding down F5
> key in my browser).

I sent to my HttpService #setDebugMode and tried it in Windows XP. I 
encountered same problem - that is primitive failed in 
Socket>>primSocket:sendData:startIndex:count:

According to this post: 
http://article.gmane.org/gmane.comp.lang.smalltalk.squeak.seaside/1228/ 
I tried "TcpListener backlogSize: 100" and it seemed it cured the problem.

> Is this the result of limited number of sockets in Windows 98? I tried
> similar test with Twisted Python frameword and there didn't seem to be
> any problems. When running the server under Linux, in standard mode
> (not #debug) will there be problems like this if the traffc is high?

Someone on Linux could try this "simple load test", though it's also a 
test for browser's event dispatch mechanism as well :)

> If the mode is not #debug, are all the exceptions correctly discarded?

It seems it might be the case; check comment in 
HttpAdaptor>>writeResponse:for:

-- 
Kamil



More information about the Squeak-dev mailing list