Glassfish could become the killer appserver for Java EE 5...

I'm working with glassfish since several months and it seems to be rock solid. Redeployment (usually a critical stuff, because of reloading of classes) is working pretty well. I'm deploying several times a day - without any side effects. There are also other opensource appservers out there, which are robust and usable. But Glassfish is more interesting for production and so commercial use.

What's unique in Glassfish:

Human-readible/usable admin console:

for real world production environments it is often not enough to provide a JMX-console or a text/XML configuration file.
Most of the administrators would like to work with more comfortable interface. Working direct with configuration files could even become dangerous in production.

Sufficient monitoring and diagnostic capabilities:
The performance of session beans calls can be monitored. Also very usable is the Call-Flow ability. Here you can monitor
the invocation path (e.g facade, bean1, bean2) with performance. This is very usable for production and also development.

Commercial support available:
I suppose glassfish is supported by Sun and commercial support can be bought (I'm not sure about this). You should not underestimate commercial support in real world.
In most cases there are only politicial reasons, but they also have to be considered.

Glassfish is well documented, training is also available available.

The netbeans 6.0m1 integration is also good but not crucial for production. In the development phase you can control the appserver
from netbeans 6.0. It is also possible to "see" already deployed beans and intercept logfiles.
Also useful: the database explorer module (see: runtime settings)

Glassfish is the first, opensource application server I know, which comes with usable admin UI and good diagnostic/monitoring
capabilities. This makes glassfish also interesting for commercial projects.

What I miss is the capability for monitoring JPA-/CMP3-entities and clustering (will come with V2).

In the next time will realize some load-, stress- and robustness tests for glassfish's ejb-container. After passing, it would be in my opinion fully capable to
be used also in "mission critical" projects.


for the best NetBeans support (full EE 5), you need to use NetBeans 5.5 Beta2.
The latest EE 5 support in not in the 6.0 branch so far, and the whole purpose of the Nb 5.5 release is to deliver the tooling for Java EE 5 support, and of course GlassFish.

Posted by ludo on August 09, 2006 at 11:44 PM CEST #


I'm using now netbeans 6.0m1. This version comes with the support in the "Runtime"->Servers->Sun Java System Application Server tab. It is absolutely sufficient for me (and also great), because I'm generate now the whole Java EE 5 business tier. So I do not need special wizzards etc...
Perpahs one improvement: it would be great to see also the monitoring and diagnostic data,

Thank you,


Posted by Adam Bien on August 10, 2006 at 11:21 AM CEST #

You've been "InfoQ'd" :-)

Posted by Stefan Tilkov on August 15, 2006 at 11:17 AM CEST #

THank you for InfoQueing me :-),


Posted by Adam Bien on August 15, 2006 at 01:04 PM CEST #

I am the lead for the callflow feature in glassfish. Somewhere in the next month or so - I will be putting in performance changes that will make callflow fly!! So look out.

We are also in process of determining features for If you need anything let us know and we can look at getting those in.

Appreciate your kind words...

Posted by Harpreet on August 18, 2006 at 12:46 AM CEST #


I will definetely stay tuned and check out the new features. Thank you!

Posted by Adam Bien on August 20, 2006 at 04:41 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments