The Tomcat Expert community is a project sponsored by VMware SpringSource aimed to help improve enterprise adoption of Apache Tomcat. Over the past two years, we’ve put out nearly a hundred unique articles from our pool of experts to help users understand more about how Tomcat works and how you can use it more effectively to power business critical applications. We’ve covered new functionality in Tomcat 7, including posts on the jdbc-pool, parallel deployment, and the WebSocket implementation. We have also covered a number of other common questions ranging from the basic "Is Apache Tomcat an App Server?" to the detailed "How do I decide between mod_jk, mod_proxy_http, and mod_proxy_ajp?".
A new question we are hoping to answer for our community is, “How can I find quality candidates to help on my Tomcat deployment?” – and we aim to do this by offering the ability for employers to post available tomcat jobs, as well as the ability for members to find jobs and to apply for them directly from our community site.
Users will need to create a login account in order to access the job posting form. Users can post an unlimited number of jobs, however until a job poster earns enough karma, each job will need to be approved by a tomcatexpert administrators to ensure the job feed is filled with quality jobs. Jobs should be related directly to the configuration, management and operation of Apache Tomcat; however, the roles can go beyond the traditional system administration and web operations roles to include java or Spring developers, instructors, technical sales engineers, and software product or architect roles that depend on Apache Tomcat. Employers have the option to have TomcatExpert email candidate submissions which include links to the candidate’s TomcatExpert profile, or to be redirected to your company’s submission process.
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.28.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies.
This release is includes may improvements as well as a number of bug fixes compared to version 7.0.27. The notable changes include:
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.27
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This release is includes significant new features as well as a number of bug fixes compared to version 7.0.26. The notable changes include:
Please refer to the change log for the complete list of changes:
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Note that this version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures.
We are trying to deploy 2 versions of the same application on Tomcat 7 to test its parallel deployment features for our application.
Not meeting with success, I was looking for a definitive guide for parallel deployment on Tomcat 7.
Our application is a JSP based application but we can have changes often.
Announced this morning by the Apache Tomcat team:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.21
Apache Tomcat 7.0.21 includes security fixes, bug fixes and new features compared to version 7.0.20 including:
Apache Tomcat 7 contains a number of new features around database connection pooling, which help administrators keep their application available and serving content, collecting customer information, and supporting their applications. The main one that has garnered a lot of attention is the new JDBC Connection Pool feature introduced by Filip Hanik last year. Another connection pool attribute not yet discussed here on TomcatExpert.com is the new closeMethod for speeding up the closing of JNDI resources that would otherwise be closed during garbage collection.
This feature stemmed from a common challenge for applications that make use of database connection pools attached to databases with limited connections allowed. For instance, if a database allows 50 connections, and an application uses a connection pool of 50 connections, in theory everything should work. However, if the application is reloaded, the existing open connections in the old pool would not close until they have been garbage collected. So the new application connection pool while configured for 50 connections, could run out at 37 if the old connection pool had 13 connections open.
Announced this morning by the Apache Tomcat team:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.20
Apache Tomcat 7.0.20 includes bug fixes and the following new features compared to version 7.0.19:
Please refer to the change log for the complete list of changes: http://tomcat.apache.org/tomcat-7.0-doc/changelog.html
Note that this version has 4 zip binaries: a generic one and three bundled with Tomcat native binaries for Windows operating systems running on different CPU architectures.
Downloads: http://tomcat.apache.org/download-70.cgi
Migration guide from Apache Tomcat 5.5.x and 6.0.x: http://tomcat.apache.org/migration.html
Thank you,
-- The Apache Tomcat Team
13 months ago today marked the initial release of the Apache Tomcat 7 beta. Proving itself to be very backwards compatible with Apache Tomcat 6, Tomcat 7 is wealth of add-on features and bug fixes that purely builds on the success of Tomcat 6. Many of these features were not around 13 months ago, many of which we have covered here including:
Originally presented in the SpringSource S2F Forum in Amsterdam, Mark Thomas recorded a new update on the overall status of the Tomcat 7 project for the Tomcat Expert community. This update is slightly more current and gives good insight as to what is now in Tomcat 7 and what will be coming (and how to influence what gets worked on!). Some interesting points Mark brings up:
This Apache Tomcat 7 update was originally delivered at the SpringSource S2G Forum Series in Amsterdam on May 26, 2011, by SpringSource engineer and the Apache Software Foundation's Apache Tomcat 7's release manager, Mark Thomas.
Apache Tomcat 7 includes several security updates that further harden the application server that came directly from the Bugzilla queue. One new feature, the Security Lifecycle Listener, helps ensure that Tomcat is started in a reasonably secure way.
One user cited that while all administrators worth their salt should know that it is irresponsible and incredibly insecure to run Tomcat as the root user to the system, Tomcat still allows the server to start under root. Although this problem is largely contained to Linux systems, the fix had to be applicable to all operating systems. Therefore, the fix that was implemented was to create a list of users that are not allowed to start Tomcat. Tomcat checks to see if it is running as one of those users, and if it is, it shuts itself down.
A secondary check after the user is validated as a secure user, is to check that any files written by Tomcat (such the contents of an expanded WAR) are created securely. As a minimum, these files must not be world writeable. In some environments it may be desirable to restrict this even further such as read/write for owner, no access for anyone else. The permissions for created files are controlled by the current user's umask. If the umask is not restrictive enough on the running user, this too will prevent Tomcat from starting.
Popular Links