We’re pleased to announce the immediate availability of our newest release of Tcat Server 6. This new release includes many fixes, in addition to bundling the Apache Software Foundation’s official release binaries of the newest Tomcat release, version 6.0.26.
Here is a summary of the changes and fixes that are included in the new version of Tomcat, since our last release of Tcat Server 6:
- Aggressive webapp / JDK memory leak handling. This is a large and important set of fixes.
- Better HTTPS security. This includes a workaround for the HTTPS vulnerability CVE-2009-3555.
- Major updates and bug fixes to Tomcat’s database connection pooling code. This includes performance fixes, exception fixes, and more.
- Improved Servlet session edge condition handling.
- Improved support for JMX via a new JmxRemoteLifecycleListener and additional JMX-related bug fixes.
- Fixed an obscure bug that caused the use of the vi editor to erase webapps. Yes, you read that right.
- Fixed quite a few thread safety bugs. This prevents bad behavior in high scalability situations.
- Many clustering bug fixes and improvements (a true distributed community effort).
- Upgraded and improved Tomcat’s Windows installer. Now fully supports 64-bit Windows installations, and the installer software has been upgraded.
- The Manager application has a new “find leaks” feature.
- Fixed potential DOS vulnerability introduced in version 6.0.25.
- Improved shutdown behavior of JULI logging – this fix ensures the correct shutdown order.
- Avoids logging of false positives of thread local memory leaks. This is important if you have been getting many of these messages about your webapps while running on Tomcat 6.0.24.
- Many additional bug fixes, including scalability and performance fixes.
In addition to these improvements, Tcat Server’s code has been improved in a number of areas, including:
- Configuration Management
- Deleting a server profile that is currently in use makes the console malfunction
- Fixed a bug that caused the console’s environment variable list to show duplicate entries
- External changes to JAVA_OPTS did not take effect on Windows
- Deployment to a server group containing more than one server failed on non-Windows OSs
- Updating the same version of an artifact with new content via the REST API is now supported (improved Maven support)
- REST API
- Canceling the action of killing a thread now behaves as intended
We encourage you to download and try this new release of Tcat Server 6. We believe you will enjoy its simplicity, and flexible capabilities. And as always, we’d like to hear your feedback about Tcat Server. Enjoy!