Has anyone else observed fproxy being unable to serve a lot of simultaneous requests? I often note that some fproxy requests hang for hours, but until now I assumed the node was at fault. Recently, however, I noticed that fproxy was incapable of serving the gateway page after I had started a lot of requests. Cancelling the other requests in the browser caused the gateway page to appear.
The other servlets running on other ports were functioning normally throughout, and the node's diagnostics showed zero overflow/insufficient threads occurrences. -tc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 240 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020208/0336afad/attachment.pgp>
