Grizzly releases are always decided by the community and sometimes a bug fixed in Grizzly may takes couple of weeks before they get integrated into GlassFish.

Right now GlassFish v3 build on top of Grizzly 1.8.6.2. We are actively working on our next release, which is 1.9.0, and that release as an example contains significant performance improvement with our Comet implementation. For people that want to test the current Grizzly SNAPSHOT jar with v3 right now, you have to execute some magic to make it work. We are working to make it much more simpler, but for now here is how it works. In v3, Grizzly classes are re-packaged (to conform to OSGi). Modules grizzly-framework, grizzly-http and grizzly-utils.jar are repackaged inside grizzly-module.jar (located under ${glassfish.home}/modules/). All other modules (grizzly-comet|cometd|messagesbus etc.) are repackaged inside grizzly-optionals.jar (located under ${glassfish.home}/modules/). So if you want to update a specific module, just do (let's use the comet module as an example):

% cd ${glassfish.home}/modules
% wget http://download.java.net/maven/2/com/sun/grizzly/grizzly-comet/1.9.0-SNA...
% unzip grizzly-comet-1.9.0-SNAPSHOT.jar
% jar uvf grizzly-optionals.jar com
// Restart GlassFish. 

This is quite simple, but would have been much easier is GlassFish were using directly our OSGi bundles. We aren't there yet, but we will eventually :-)

technorati: grizzly glassfish