The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.29.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Apache Tomcat is an open source software implementation of the Java Servlet and JavaServer Pages technologies.
This release corrects a small number of regressions introduced in the 7.0.28 release and takes account of several recent clarifications from the Servlet Expert Group as well as containing a handful of bug fixes and small improvements compared to version 7.0.28. The notable changes include:
SpringSource tc Server provides enterprise users with the lightweight java app server they want along with the streamlined configuration, advanced performance monitoring, and professional support businesses need. Built as a drop-in replacement for Apache Tomcat, tc Server will instantly upgrade your custom-built and commercial software applications to serve your enterprise needs.
Download your free trial, and try it today! Learn More »
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:
VMware released an update to their vFabric Suite 5.1, an integrated family of components that streamline how companies build, run and manage Java / Spring applications whether on-premise or in the cloud. Several of those components include enhanced support for Apache Tomcat 7.
The new version of the popular web infrastructure management software, Hyperic, comes with a new plugin that adds support for Apache Tomcat 7. In addition, Hyperic also introduced support for detailed configuration history tracking that is included by default in the new Tomcat 7 plugin. This history allows administrators to not just identify that a file was changed somehow, but zero in on exactly what text was added, deleted, modified or in the case of file names, renamed. This new feature will save administrators and developers significant time when trying to troubleshoot problems and identify “what changed”. See the full post on how the latest version of Hyperic gives Apache Tomcat an Upgrade on the Hyperic blog.
With the Apache Tomcat 7.0.27 release, the Apache Tomcat team introduced a WebSocket implementation. In a previous post, we took a look at what the WebSocket implementation means, including what benefits and limitations they present. Today, we will discuss specifically how WebSocket is implemented in Apache Tomcat 7.
Since WebSocket is a protocol sent over TCP after an initial HTTP handshake, you could effectively implement WebSocket using Tomcat’s Comet implementation. There is a back port to Tomcat 6 suggested that does exactly that with very minor changes.
The Apache Tomcat team however decided to go with a more substantial implementation with changes to the core of Tomcat’s network and protocol implementation. The reason for this was memory and scalability based. If Tomcat can recycle the HttpServletRequest/Response objects after the initial handshake, each WebSocket connection will take up less memory in the Java heap. It also opens up the Tomcat container for other future protocols that utilize the HTTP Upgrade feature.
The WebSocket implementation from an API standpoint is fairly straightforward. You really can only do two things:
With the 7.0.27 release the Apache Tomcat team introduced a WebSocket implementation. WebSocket has received a lot of hype, and has been much anticipated by Tomcat users. Let’s take a quick look at what web sockets are, what benefits and limitations they have and how they are implemented in Apache Tomcat 7.
WebSocket is considered the next step in evolution of web communication. Over time, communication has evolved in steps to reduce the time and data throughput for the application to update a user’s browser. The evolution has looked a little like this:
Each of these steps had their benefits and challenges. Apache Tomcat 6 implements bi-directional communication over HTTP using its Comet Processor. This implementation allowed for asynchronous event driven request processing as well as bi-directional communication. This implementation had a few limitations.Blog : Apache Tomcat 7.0.29 released
Download tc Server
Blog : Apache Tomcat 7.0.28 released
Blog : VMware vFabric Suite 5.1 Expands Support for Apache Tomcat 7
vFabric Hyperic
Blog : How Apache Tomcat Implemented WebSocket
Blog : WebSockets in Tomcat 7
What is a WebSocket?
Popular Links