Recently I was working on a bug where Grizzly was leaking memory. From the code, I was convinced the leak wasn't in Grizzly (of course :-))! The problem was occurring when GlassFish was stressed during three days. After approximatively 16 hours, some components in GlassFish weren't able to get a file descriptor, so I've suspected a memory leak somewhere in other's code ;-). The test was using JDK...
As described in part II, it is possible to extend the Grizzly Http Engine by writting Pipeline, Algorithm, Handler and AsyncHandler. By default, every HTTP connection are executed synchronously, e.g the request is parsed, the servlet executed and the response flushed to the browser. There is situation where this model doesn't work, e.g. when a business process is calling out to another one over a...
