By ekabanov
via zeroturnaround.com
Published: Sep 22 2009 / 11:01
The Java EE Container Redeploy & Restart Report comes from a survey conducted over the summer, with over 1100 Java EE developer respondents. It analyzes time spent on the Redeploy and Restart process, and compares the following containers: GlassFish, Jetty, Tomcat, WebSphere and WebLogic. Among other results, this report shows that Java EE developers are spending 3 to 7 work weeks a year on redeploys and restarts, depending on their container of choice.
Comments
sateesh.narahari replied ago:
Great data and report...
The sad news seems to be that 50% of the survey respondents are spending too much time starting/restarting, redeploy of their webapps, since they are using either JBOSS, WLS or WAS ( I am guessing, its primarily due to legacy reasons). The good news is that several of these users will save time, money and resources if they migrate to Apache Tomcat, and from anecdotal evidence that seems to be happening more now.
For anyone looking for guidance on how to move to Tomcat from WLS, here are some thoughts from a colleague: http://blogs.mulesoft.org/2009/09/whitepaper-migrating-from-weblogic-to-tomcat/
pzoio replied ago:
This article provides some better than anecdotal evidence about what we all knew, that waiting for application restarts is in many projects a real time drain. It's worth mentioning that the lost productivity is not only in the form of the wait time, but in the way that this wait time distracts you and forces you to break your concentration while looking for something else to do while waiting for your application to reload.
Another solution, apart from JRebel of course, is Impala - http://code.google.com/p/impala/ - which uses dynamically reloadable modules with Jetty running in Eclipse to allow almost instantaneous application reloads.
Voters For This Link (23)
Voters Against This Link (2)