One of the good things about Apache Tomcat is that it is world’s most efficient and effective application server for running web applications. Legacy Java EE application servers can be more trouble than they are worth due to their inherent complexity and feature bloat.
In January of this year, the Apache Software Foundation released, Tomcat 6.0.24 , which made major improvements in finding and preventing memory leaks in web applications. Today the ASF released Tomcat 6.0.26, which is an improvement over 6.0.24. (If you are wondering what happened to 6.0.25, that release was deemed not suitable to be released).
Here are highlights of the changes that went into this release since 6.0.24:
– The Manager application has new find leaks functionality, which would help you detect memory leaks of your webapps on stop, reload or undeploy.
– Fixed security hole introduced in 6.0.25
– Improved shutdown behavior of JULI logging – this fix ensures correct shut down order
– Avoids reporting of false positives of thread local memory leaks – this is important if you have been getting tons of these messages for your webapps while running on Tomcat 6.0.24.
For the full list of changes that went into the release, read the changelog here.
We at MuleSoft have taken a position that Tcat Server will support new releases of Apache Tomcat as soon as they are released. With that, I am pleased to announce that we are supporting Tomcat 6.0.26 (as well as previous versions, all the way back to 5.5). Customers using Tcat Server can download Tomcat 6.0.26 directly from the ASF and use it with Tcat Server immediately. Read about how to install Tcat Server on an existing Tomcat server here.
Because Tcat Server is built on 100% Apache Tomcat, with no modifications to the core binaries, it is able to support the latest versions of Apache Tomcat on the same day that they are released. As far I know, Tcat Server is the only enterprise Tomcat product in the world who can make this claim. While there are other products for Tomcat, they are either modified or forked versions, which creates an unnecessary and expensive vendor lock-in.