Monday Jan 03, 2011

Which Java EE 6 App Server ? - JBoss 6.0 or GlassFish 3.x

It's been over a year that Java EE 6 was released in Dec 2009 along with GlassFish as the Reference Implementation.  JBoss contributed two new specifications to the Java EE 6 platform - JSR 299 (Contexts & Dependency Injection) and JSR 303 (Bean Validation) and contributed in multitude of other ways to make the platform successful, many thanks for that. RedHat released JBoss 6.0, their first Java EE 6-compliant app server (no production support and only Java EE 6 Web Profile) last month, a very hearty congratulations to them!

Resin is also making good progress and should be coming out soon too, Websphere 8.0 Beta already has support for Java EE 6, Oracle WebLogic coming out later this year. Read "From 2 to 8: Java EE 6 App Servers" for couple of months old status on Java EE 6 compliance.

This blog highlights some key differences between the GlassFish 3.x and JBoss 6 (based upon publicly available information and some basic experiment on my personal machine):

Features/AppServer GlassFish 3.0.1 JBoss 6.0
Compliance Full Java EE 6, and Java EE 6 Web-Profile Java EE 6 Web-Profile Only
Download Size 33-52 MB for Web Profile, 34-85 MB full Java EE 6 181.3 MB
Installer Zip and .sh/.exe installers Zip only
Release Maturity 1 year+ About 1 week
Commercially Supported Yes No
IDE Integration NetBeans, Eclipse, IntelliJ Eclipse (primarily), NetBeans
Web-based Admin Console Yes Yes
CLI Administration Yes No
REST-based Administration Yes No
Clustering Coming in 3.1 Yes
Update Tool Yes No
OSGi Native Configurable
Startup Time (3 consecutive start/stop on 4GB MacBook Pro with default settings) (7-12 seconds)

GlassFish Server Open Source Edition 3.0.1 (22) startup time : Felix(10330ms) startup services(1680ms) total(12010ms)
Felix(5557ms) startup services(1149ms) total(6706ms)
Felix(5729ms) startup services(1576ms) total(7305ms)

(29-25 seconds)

JBossAS [6.0.0.Final "Neo"] Started in 35s:210ms
Started in 34s:498ms
Started in 29s:532ms

Docs Comprehensive Minimal, mostly placeholders and in some places pointing to older 5.x docs.
Maven Listed on download page. Could not find them listed here.

Let me know if any of the points need correction.

And now some miscellaneous bullet points ...

  • JBoss Download page says "This is a community project and, as such is not supported with an SLA.". Clicking on the Download link again shows a warning "Community projects represent the latest development releases and are not supported". So you can download JBoss 6 and use it for development but would you like to use an unsupported product, with no SLA, in production ?

  • The first Java EE 6 implementation, i.e. GlassFish, is available and tested in multiple scenarios for over a year.

  • The zip-install required manual intervention:

    inflating: jboss-6.0.0.Final/docs/licenses/Gnu Lesser Public License - lesser.html  
    replace jboss-6.0.0.Final/docs/licenses/GNU Lesser General Public License -
     lgpl.txt? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
      inflating: jboss-6.0.0.Final/docs/licenses/GNU Lesser General Public License -
     lgpl.txt
    
  • Only Java EE 6 web profile compliance in JBoss means there is no way to use other Java EE features yet. And so you are stuck if your needs grow beyond Web Profile.
  • Going to http://localhost:8080/admin-console starts a hidden Java window as well, found it slightly weird!
  • The release notes is just a buglist with no instructions on supported platforms etc.
  • Stopping the container took over a minute, 1m:3s:692ms to be precise. And this is when only Admin Console was accessed and no app was deployed.

The articles like "New JBoss puts Java EE 6 to Work" by PC World and others with similar heading are misleading when they say "one of the first enterprise-grade application servers to fully support Java EE 6". How can an App Server be enterprise-grade and yet not offer commercial support and minimal documentation ? And also Java EE 6 is already put to work in multiple GlassFish deployments so not sure what it means "puts to work".

Both WebLogic and GlassFish are equally strategic for Oracle. If you want to use open source, light-weight (highly modular, smaller size, high speed, not "not enterprise ready") development/deployment, and cutting edge Java EE 6 features then pick GlassFish. If you want integration with Coherence, Fusion Apps, sophisiticated deployment scenarios then pick Oracle WebLogic. And WebLogic builds upon the innovation done in GlassFish by sharing multiple components anyway.

In addition, the current release of WebLogic Server (11g 10.3.3) has support for some of the key Java EE 6 standards like JSF 2.0 and JPA 2.0. The upcoming WebLogic release (11g 10.3.4) will have support for some other Java EE 6 specifications as well. And Java EE 6 compliance in WebLogic is also coming later this year.

Where are you deploying Java EE 6 applications ?

Technorati: javaee6 glassfish jboss comparison

Tuesday Oct 20, 2009

Comparing GlassFish and JBoss: Helping you decide!

The majority of developers building Java applications will find that the GlassFish application server offers distinct advantages compared with JBoss. This paper summarizes the features and capabilities that make GlassFish a superior choice for building, deploying, and managing enterprise-class Java applications and Web services.


Here are some other recently published GlassFish white papers:

A list of white papers & webinars published earlier this year is available here. An updated list is always available in the Resources section of GlassFish Portfolio.

Technorati: glassfish jboss whitepaper

Friday Jun 26, 2009

supercrud.com in Brazil picked GlassFish - Find out why!


Vinicius Senger, founder of Globalcode - a Java training/consulting company in Brazil, is running supercrud.com on GlassFish.

He is a Java EE architect, consultant, trainer, and do Java EE related research as well. He is a JSF 2 Expert Group member, find NetBeans and GlassFish integration amazing and feels its getting better all the time. He runs supercrud.com on GlassFish. The reasons to pick GlassFish:
  • Much easier to install
  • Easy to manage (data sources, EJBs, redeployments) using web-based administration console
  • Don't use clustering today but know it's another good feature
He is seeing lot of Brazilian companies and developers moving to GlassFish because it's
  • Faster
  • More modular
  • Faster redeployment
  • Better integration with NetBeans/Eclipse
Hear the short interview recorded at FISL earlier this week:



A formal production story will be published soon as well. Thanks Vinicius for the interview!

Technorati: conf brazil fisl javali glassfish jboss story

Sunday Jun 24, 2007

Why GlassFish over JBoss ?

A lively discussion happened on GlassFish Forums where a user asked for pros/cons for GlassFish vs JBoss. A community user explained his reasons to choose GlassFish over JBoss. Here are they key points:

  1. Admin GUI and CLI alone are true differentiators.
  2. Java EE5 with EJB3 is much better to work with and GlassFish is JavaEE5 compatible, of course it's the Reference Implementation as well.
  3. Seamless integration with NetBeans.
  4. Solid and consolidated documentation.

Some other quotes are:

  • "overall GF is just plain easier to use and that's my major pain point."
  • "The new clustering looks spectacular"
  • "GF is really a joy to work with and we haven't had any major problem using it"
  • "you will be up to speed and productive more quickly on GF than JBoss, and just as important, you will stay that way"
  • "because of JEE 5, EJB3, and the JPA, and leveraging that technology, our applications run better, and are easier to maintain. GF is not the sole perveyor of such technology, but the combination and integration of the whole thing: GF, NB, EJB3, and the low learning curve and overall ease of use makes the entire package a "performance win" for our apps as is"
  • "The best part is the server is handling more and more of the stuff we need to do and we have to work around it less and less."

And if these are not enough for you to choose GlassFish, here is a more detailed list of Why Use GlassFish ?.

And we see GlassFish as "GlassFish is WebLogic Features and Performance at JBoss's price" except we are shooting for better Features and Performance than WebLogic!

Technorati: glassfish jboss opensource

Wednesday Jan 24, 2007

JAX-WS on JBoss

Read about a customer experience on using JAX-WS RI on JBoss on the server side and JAX-WS runtime with Java SE 6 on the client side.

An important point to note in the article is the 1000% performance gains between EA and and more recent versions of JAX-WS. Not all of this gain may be due to JAX-WS :)

Technorati: JAXWS JAX-WS JBoss Web services

Tuesday Oct 31, 2006

Another Web services stack comparison

Another Web services stack comparison at JBoss wiki and GlassFish is looking really good. Read more details about the feature support here.

Technorati: WSIT JBoss J2EE

About

profile image
Arun Gupta is a technology enthusiast, a passionate runner, author, and a community guy who works for Oracle Corp.


Java EE 7 Samples

Stay Connected

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today