Monday Mar 05, 2012

GlassFish 3.1.2 Updated Components (Final)

Now that GlassFish 3.1.2 has been released, it's time to check on the exact list of updated components (one of the important themes in pretty much every release).

• JSF/Mojarra 2.1.6
• Grizzly 1.9.46
• Metro 2.2
• Jersey 1.11
• Shoal 1.6.17
• EclipseLink 2.3.2
• Message Queue 4.5U2
• OSGi Core 4.3.0
• Update Center 2.3.5
• Hibernate Validator 4.2.0-FCS
• JavaDB
• Weld 1.1.4.Final


About half of the bugs squashed in this GlassFish 3.1.2 release were through the integration of those recent components.

Wednesday Feb 08, 2012

Grizzly now with AHC-powered WebSocket client

With the recent release of Async HTTP Client (AHC) 1.7.0, Ryan has details on how this impacts Grizzly to essentially provide support for WebSocket clients.


Ryan covers the new grizzly-http-client Maven artifact for AHC and introduces UpgradeHandler, WebSocketListener, WebSocket interfaces for WebSocket support with a short but complete working sample.

With this release, Grizzly now provides support for both sides of the WebSocket wire. Both GlassFish 3.1.2 and of course 4.0 will offer support for the final version of server-side WebSocket. if you're eager to use the technology in your application, then you should try out recent builds of 3.1.2 and let us know how things work for you.

Tuesday Dec 20, 2011

Grizzly 2.2 is here, WebSocket inside! (& more)

As you may have heard the WebSocket protocol, often described as one of the key elements of HTML 5, has finally been blessed (check out RFC 6455).

Well, it only took Grizzly 10 days or so to implement this final specification and ship Grizzly 2.2 (granted it's been keeping up with all the interim releases).


In other important addition to this release, the Grizzly Async HTTP Client will soon hit 1.7.0 and also offer WebSocket support! Non-Blocking Sendfile Support and write I/O Thottling as a protection against async write queue overloading are also new in this release.

This version of Grizzly will be integrated into GlassFish 4.0 (and may already be in the trunk by the time you read this), while 3.1.2 will ship with 1.9.42 (or later), both do offer support for RFC 6455.

How many more server-side implementations out there supporting the WebSocket protocol?

Sunday Dec 18, 2011

Updated Components in GlassFish 3.1.2

One of the important goals of the upcoming GlassFish 3.1.2 release is to update the sub-components to their most recent versions.

This in itself squashes a number of bugs filed against GlassFish and brings individual new features to a fully integrated and supported product.

Here is the target list of components in this next GlassFish release :

Original Tesla Engine Photo from

• JSF/Mojarra 2.1.6
• Grizzly 1.9.42
• Metro 2.2
• Jersey 1.11
• Shoal 1.6.15
• EclipseLink 2.3.1
• Hibernate Validator 4.2.0-FCS
• Weld 1.1.4

Should there be any changes, this will be documented on the GlassFish Wiki (which now has all the redirects in place following the recent move).

Friday Sep 16, 2011

Jersey 1.9.1 & Grizzly Async (HTTP) Client integration

With the release of Jersey 1.9.1, "conference-driven development" (CDD) is not an empty word. In his blog post Martin shares the Jersey-based JavaOne OAuth Hands-on Lab requirements that lead to this release while the full release notes are here.


Meanwhile, Grizzly 2.x is making good progress and the latest trunk includes integration of Jean-François' Async HTTP Client Library (AHC). Ryan, from the Grizzly team, details the status of the ongoing work on his blog, including plans for a Grizzly bundle that includes the HTTP Codec library (grizzly-http), the AHC library and its Grizzly provider. This should all be out in stable form by Grizzly 2.2.

Tuesday Aug 23, 2011

Back to school - GlassFish tabsweep (Grizzly, Homebrew, Jelastic, EclipseLink, ...)

If, like TheAquarium, you were out for the past few weeks, you may have missed the following news and links around GlassFish.

Following the release of GlassFish 3.1.1 earlier this summer, we now have the bits available in Homebrew, courtesy of Julien. That same version of GlassFish is also now available in Jelastic, a new PaaS player.

Rapids in small French river

In other GlassFish-related news, EclipseLink's Shaun notes that GlassFish 3.1.1 Ships with EclipseLink 2.3!, Bhakti has a quick tip to use Felix Gogo to inspect jar/bundle dependencies, and Masoud discusses how to use the RESTful admin interface instead of JMX/AMX.

On the Grizzly front, Ryan announces the release of 2.1.2, while Oleksiys continues his Grizzly 2.x series of post, this time with the use of the HttpServer API to write an asynchronous HTTP Server: part 1, part 2.

Sunday Jul 24, 2011

Using Grizzly 2.x as a simple HTTP server

Oleksiys, the Grizzly technical lead has started a series of blog posts about Grizzly 2.x.

He discusses how familiar the APIs should look to anyone that has used Servlets and how simple it can be to create an HTTP engine and start serving static or dynamic requests with Grizzly. If you try for yourself, you'll also see how snappy Grizzly can be.


Grizzly 2.0 was released in Feb (2011) with 2.1.1 being the latest available stable version. Check out this "Getting Started" page. This 2.x branch will be integrated into the next major release of GlassFish.

Tuesday Apr 26, 2011

Grizzly 2.1 ships - AJP, WebSocket, LZMA and more

Over on his blog, Ryan Lubke announces the release of Grizzly 2.1 (né 2.0.x) with the typical set of bug and performance fixes but also some new features such as AJP support, Multipart Form Submission Processing and LZMA compression. This version also includes updated support for the WebSocket protocol (now on draft 06).


This announcement blog also has a list of useful resources for users while documentation is linked off of the project main page.

Grizzly 2.x will be integrated into GlassFish 3.2 later this year while the current GlassFish 3.1 version ships with Grizzly 1.9.34.

Thursday Mar 24, 2011

WebSockets support in GlassFish 3.1 (and Grizzly)

There is no need to wait for Java EE 7 or GlassFish 4.0 to use the WebSocket protocol. As we've covered in the past the bottom line is that you can use WebSockets today with GlassFish 3.1.


GlassFish 3.1 (Grizzly 1.9.32) implements the -76 version of the WebSocket Protocol and was used to created this series of screencasts. Justin has many more details on what can be done with the stable and supported release of GlassFish. This version of WebSockets is reported to be supported by Google Chrome 6, Safari 5.0.1, and Firefox 4.0 (although disabled by default).

As browsers move to implement newer versions of the WebSocket protocol, you'll need to get into bleeding edge territory (i.e. not supported) and use a more recent version of Grizzly. Either update GlassFish 3.1 to the fresh from the oven version 1.9.33 (see Justin' blog about this) or use grizzly 2.0 directly. The -06 version in particular is supported in 1.9.33. Whichever version you end up using, don't forget to enable support for WebSocket in GlassFish.

Check out also this recent slide deck from Justin.

Sunday Mar 20, 2011

Grizzly 2.0 is here!

With the release of GlassFish 3.1 and the new Java EE 7 JSRs being filed, it was easy to miss other announcements such as the release of Grizzly 2.0.

Grizzly 2.0 features many brand new APIs (it's called 2.0 for a reason!), updated WebSockets & Comet and documentation (start with the Getting Started).

Grizzly logo

As it is often the case with Grizzly, performance is a key improvement and Oleksiys shares some informal yet very encouraging results in his blog post.

Given the timing, this version clearly didn't make it into GlassFish 3.1 (which uses Grizzly 1.9.32). If you're really interested in testing out the newer 2.0, there is an unsupported way to add it to your existing 2.x or 3.x GlassFish, check out the mailing list archives.

Friday Nov 05, 2010

First Wave of Java.Net Migration

A few weeks into the acquisition, Ted Farrell announced plans to migrate Java.Net to Kenai infrastructure. For multiple reasons, it took us a bit to implement this, but last week we started with a first wave of GlassFish projects and a bit later Sonya provided Additional Details about the Migration.

Although the migration also involves some CMS changes the main focus right now is on the Forge Migration, from CollabNet Infrastructure to Kenai Infrastructure.

The projects involved in the first wave included Jersey, Metro, Grizzly, Atmosphere, JAX-WS, OpenMQ and several more. The intention was to do a quick migration but that has been delayed, with the current completion target date being Monday. Once the first wave completes, we will start migrating the rest of GlassFish and then other Java.Net projects.

Some additional details at:

Saturday Sep 04, 2010

Friday Tips #6: Port Unification, ASAdmin Options, PrimeFaces Support, Grizzly 2.0...

Here are some tips that have been recently published on Java EE 6 & GlassFish:

Informational Sign

• Port Unification in GlassFish 3 - Parts 1, 2, 3 and 4
asadmin common options (remote, secure, log)
File Upload with Servlet 3.0
REST services with Jersey and Spring 2.5
Glassfish V3 Installation on Linux (for beginners…)
How to use GlassFish application versioning
Grizzly 2.0 now has JMX support
Grizzly 2.0.0 release candidate 1 is now available!
PrimeFaces Support in NetBeans 6.10
PRLB feature in GlassFish 2.1.1
Admin Console very slow in OGS 3.0.1

Let us know if you have seen or published a detailed tip like shown above and we'll be happy to share them.

Thursday Mar 04, 2010

GlassFish in February


The breadth and depth of the community is nicely illustrated by the variety of recent GlassFish-related blog posts. First, long time GlassFish supporter Masoud has a very detailed (it's actually a chapter of a book) OpenMQ from A to Z entry. On the operations side, Byron has a set of two posts on How to Run GlassFish V3 as a Service on Linux Ubuntu/Debian and a follow-up on using a non-root Service (see also thisGentoo variation by Jason), while Felipe's on provisioning GlassFish v3 resources with asadmin.

In the "nice words" category, Juliano has a nicely written "Java Enterprise Development - 2010 style" piece and Maksim says "GlassFish is becoming new de facto standard in Java applications. Development with new GlassFish v3 server and Eclipse now is really fast and comfortable. Server starts within a second, JEE6 is fully supported and hot code replacement works as it should.".

On the Java EE 6 and web tier side we have Bobby sharing a tool for exploring the platform, Aleksey discussing a "Grizzly 2.0: simple authentication example", while Justin puts GlassFish embedded to work with Wicket. Rene has a two-part article on running a Java EE 6 Client Application with Netbeans 6.8 and GlassFish V3 - Part 1: Creating a Basic Application and Part 2: Enhancing and Deploying the Application while Jacob goes through the simple setup to have GlassFish and Intellij 9 work together.

So while we wait for the GlassFish roadmap, we've seen one of the busiest month ever for February on the user mailing list and this recent message from the GlassFish Product Management "GlassFish, and by extension, Metro, are strategic Oracle products". Exciting times ahead!