Hi guys, If I recall others have also problems with sockets in Pharo, so here is the my current image, which:
- has 105 Sockets open, mostly waiting - has also >105 processes open - consumes 100% cpu - on aSocket close responds with primitive failure - image is workable, I can browse etc. - Pharo1.2.2a on Linux Sockets are waiting on Socket>>waitForConnectionFor:ifTimeOut: If I put a breakpoint in this method, most processes waiting on socket raise an exception and I can manually terminate them. CPU is then back to normal. But still 48 sockets and their processes are open. Now I debug one such process from Process monitor and immediatelly another batch of self halt exceptions are raised. Now I managed to manually close all sockets and their processes. Has anyone an idea how to avoid those sockets being deadlocked on some waiting? It seems that they timeout but are soon back. They seem to timeout quite fast, is this a reason for 100% CPU? Why I cannot close them but instead a close fail with primitive failure? Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
