Top 6 Open Source Java EE Application Servers
Join the DZone community and get the full member experience.Join For Free
this is a very basic review of active and available open source java ee application servers and servlet container (web containers) to let the community know which active containers are available and what is the general status of each container. the article can simply act as a start point for anyone need to select one of them for later use in development or product. detailed comparison of these production cover many pages of a tick book.
full blown open source java ee application servers:
resin , a well known product from caucho is an open source java ee application server which has been around for quite a long time and many small and large deployment of it are serving small and large systems like dzone itself.
current stable version of resin is 3.1.9 which fully support java ee 5 and the development version which will replace the current one is 4.0.1. resin licensing schema is a bit different with other alternatives. they provide a gpl-ed version for open source distributer and evaluators while commercial usage requires paying caucho some per/cpu - per/year fees. different editions of resin is available with a different set of features and capabilities and each edition has its own pricing schema. you can find more about the different versions and licensing fees at: licensing
resin come with clustering, high availability support and benefits from an integrated caching system. similar to glassfish resin support hosting php applications using quercus.
for the administration and management, resin took an alternate path by providing a light weight monitoring application to let administrators and developers see status of different services in the application server and left the the administrators to perform administrative and configuration tasks trough configuration files.
when it come to development tools support you can expect netbeans, eclipse and intellij integration along with integration with ant, maven, and ivy.
- download link: http://www.caucho.com/download/ you can get version 4.0.1
- how to start: goto install_dir/bin and issue /resin.sh start or resin.exe start dependin on your os
- monitoring console: details: url: http://127.0.0.1:8080/resin-admin/ you will need to create a user and password to proceed further. follow the on-screen steps to create the user and password.
geronimo : the apache java ee application server which is obviously distributed under asf. geronimo lacks behind glassfish when it come to implementing new java ee specification but it benefits from a good administration console compared to jboss. clustering is available trough 3rd party products like terracotta and there is no out of the box support for clustering and high availability. geronimo is well integrated with other apache projects like servicemix and activema. current version of geronimo is v2.1.4 and fully support java ee 5 specification. commercial support for geronimo is available through ibm websphere application server community edition.
two separate distribution of geronimo is available, one with jetty as web container and the other one with tomcat as the web container. all major ides support geronimo as a development server.
- download link: http://geronimo.apache.org/apache-geronimo-v214-release.html
- how to start: goto install_dir/bin and issue ./geronimo.sh start or geronimo.bat start depending on the os
- administration console details: url: http://localhost:8080/console/ credentials: system/manager
glassfish : mainly developed by sun microsystems and benefits from a modular, and extend-able architecture. glassfish is in the front line of providing the community with new java ee specification implementation and in the same time it provides all users with features like: advanced administration channels, out of the box clustering and high availability, osgi runtime deployment and so on. using glassfish means that users can easily sign a contract and get support from sun without need to change the deployment bits. current glassfish stable version is glassfish 2.1.1 and the next major version is glassfish v3 which is a fully java ee 6 compliant and osgi based application server. the new version is due to be released on november this year. open source glassfish is accessible under cddl and gpl licenses.
glassfish benefits from integration with a wide set of sun products starting from operating system (solaris) up to the ide (netbeans). glassfish esb, open portal, opensso and openmq are some of the notable projects that glassfish is well integrated with.
another strength in glassfish is integration with sun hadb which can form a proven highly available infrastructure without spending any penny for the required software and licenses.
all major ides support glassfish as a development server and it means an easy start for developing java ee applications using glassfish.
- downlod link: https://glassfish.dev.java.net/downloads/v2.1.1-final.html
- how to start: goto intall_dir/bin and issue asadmin start-domain
- administration console details: url: http://localhost:4848 default credentials: admin/adminadmin
jboss : it was present in the open source community longer than other projects and benefits from red hat support. jboss application server provides clustering and high availability out of the box but the administration console which included in the distribution from version 5.1 is not advanced enough to let administrators manage the all application server resources . the included administration and management console is an embedded version of jopr (http://www.jboss.org/jopr). this console will acts as a single point of administration and management for all jboss technologies like esb, cache et. current version of jboss is 5.1.0.ga and next upcoming version is 5.2. jboss is distributed under lgpl and anyone interested can get commercial support from red hat. jboss community distribution and enterprise distribution are two different package and and moving from community support to commercial support means installing an alternate version of jboss named jboss enterprise middleware.
jboss application server benefits from integration with a wide range of middleware provided by jboss. this products include caching, bpm, esb, portal and so on. on the development side, it benefits from jboss developer studio (not available for free) which is based on eclipse and provide tooling for wide range of middlewares provided by jboss.
all major ides support jboss as a development server and it means an easy start for developing applications on top of this application server
- download link: http://www.jboss.org/jbossas/downloads/
- how to start: goto install_dir/bin and issue ./run.sh or ./run.bat depending on the os
- administration console details: url: http://localhost:8080/admin-console/ default credentials: admin/admin
jonas is one the flagship projects in ow2 consortium and in contrast with having less buzz in the news and blogosphere it benefits from a profound modular architecture based on osgi. jonas administration console is well designed and benefits from a slick user interface. jonas benefits form integration with jasmine for designing, deploying and administrating a clustered environment.
current version of jonas is 5.1 which fully support java ee 5, the next planned version is 5.2 which is due to be released in feb 2010 with basic support of java ee and self management. major ides like eclipse and netbeans support jonas as a development server. jonas is distributed under lgpl
- download link: http://wiki.jonas.ow2.org/xwiki/bin/view/main/downloads
- how to start: goto install_dir/bin and issue ./jonas start or jonas.bat start depending on the os
- administration console details: url: http://localhost:9000/jonasadmin/ credentials: admin/admin
jetty : jetty is considered an alternative to tomcat to some level. because of the differences between these containers architecture each of them has its user base. jetty is considered lighter, easier to embed and highly modular while tomcat is considered more feature rich. both projects benefit from a good performance under heavy load but it certainly can change from version to version and between different use cases. a cluster of jetty instances can be configured using any of gigaspaces, wadi, terracotta, etc. jetty does not have a management console and everything should go through the configuration files by adding required changes to the configuration files. a good comparison between tomcat and jetty can be found at: http://www.webtide.com/choose/jetty.jsp
- download link: http://www.eclipse.org/jetty/downloads.php
- how to start: goto install_dir/bin and issue ./jetty.sh start or jetty.bat start depending on the os
- administration console details: no administration console.
note : before attempting to start jetty add following line in the install_dir/bin/jetty.sh or jetty.bat depending on the os.
for linux, unix..:
tomcat : apache tomcat was around for past 10 years and it is the most widely used servlet container. many of the shared host providers provide tomcat hosting for their customer while you can rarely find glassfish, geronimo, jboss and jonas hosting in the internet. apache tomcat is distributed under apache license and its current version (6.0.20) supports servlet 2.5 and jsp 2.1. apache tomcat comes with a bundled management console which provides administrators with very basic configuration capabilities. most administration and management tasks should be done by editing the configuration files. tomcat is supported by any known ide and build/ deployment tools and it shows it popularity in the community. tomcat come with built-in clustering and session replication support.
- download link: http://tomcat.apache.org/download-60.cgi#6.0.20
- how to start: goto install_dir/bin and issue ./startup.sh or startup.bat depending on the os
- administration console details: url: http://127.0.0.1:8080/manager/html credentials: admin/admin
note: before starting tomcat add following line in the install_dir/conf/tomcat-users.xml inside the tomcat-users node:
<user username="tomcat" password="tomcat" roles="manager"/>
conclusion: none of this projects can fit all development and deployment plans and requirement. each of them has its strenghts and weak points compared to other 5 competitive projects. what one need to do is testing all of them and decide which one is better.
Opinions expressed by DZone contributors are their own.