TomcatExpert

Blogs

Blog : Apache Tomcat 7.0.29 released

posted by Stacey Schneider on July 8, 2012 06:59 PM

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:

  • Add support for a default error page
  • The servlet version defined in web.xml no longer determines if Tomcat scans for annotations when the web application starts. This is now solely controlled by metadata-complete element.
  • On web application start, JARs are now always scanned for ServletContainerInitializers regardless of the setting of metadata-complete

Read More

0 comments   |  

0
Rating
  |  

Developers, Operations | Apache Tomcat 7

Blog : Apache Tomcat 7.0.28 released

posted by Stacey Schneider on June 19, 2012 08:07 AM

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 minimum required APR/native library version required if the APR/native connector is used is now 1.1.24.
  • Various fixes and improvements to WebSocket support including the use of infinite time outs by default for WebSocket connections. * Various fixes and improvements to annotation scanning.

Read More

0 comments   |  

0
Rating
  |  

Developers, Operations | Tomcat 7

Blog : VMware vFabric Suite 5.1 Expands Support for Apache Tomcat 7

posted by Stacey Schneider on May 31, 2012 08:05 PM

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.

vFabric Hyperic

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.

Read More

0 comments   |  

0
Rating
  |  

|

Blog : How Apache Tomcat Implemented WebSocket

posted by fhanik on May 1, 2012 07:13 AM

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:

  1. Send messages
  2. Receive messages

Read More

5 comments   |  

5
Rating
  |  

Developers, Operations | WebSocket, Apache Tomcat 7

Blog : WebSockets in Tomcat 7

posted by fhanik on April 23, 2012 10:22 PM

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.

What is a WebSocket?

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:

  • Entire page reloads
  • Component reloads using AJAX Processing
  • Comet communication
    • Long poll– similar to AJAX, but not holding a thread on the server
    • Bi directional- two way communication over the same TCP

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.

Read More

3 comments   |  

0
Rating
  |  

Developers | WebSocket, Apache Tomcat 7

Blog : Apache Tomcat 7.0.27 Released

posted by Stacey Schneider on April 5, 2012 01:59 PM

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:

  • Support for the WebSocket protocol (RFC6455). Both streaming and message based APIs are provided and the implementation currently fully passes the Autobahn test suite. Also included are several examples.
  • A number of fixes to the HTTP NIO connector, particularly when using Comet.
  • Improve the memory leak prevention and detection code so that it works well with JVMs from IBM.

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.

Read More

0 comments   |  

0
Rating
  |  

Developers, Operations | nio, Tomcat 7, WebSocket

Blog : Integrating Jenkins and Apache Tomcat for Continuous Deployment

posted by jfullam on March 20, 2012 04:32 PM

Working software is the primary measure of progress for software development teams. This is one of the principles of the Agile Manifesto and has led agile software teams to focus on implementing the most important features of a system early and efficiently. These teams usually provide frequent deployments of the software in order to receive feature validation from the business and to show project progress. The benefits are quick and frequent feedback for the developers and congruous applications for the business.

The practice of automated continuous deployment ensures that the latest checked in code is deployed, running, and accessible to various roles within an organization. Project managers can have a place to check on project progress, testers have a view into the latest builds, developers can see the their modules working with the modules from other team members, and stakeholders can see how their requirements have been translated into working software. Tomcat and tc server easily integrate with continuous integration servers to allow agile teams to realize continuous deployment while utilizing a lean application server (another practice of agile teams). You can start practicing continuous deployment very quickly using Tomcat or tc server, Jenkins, and your source control system of choice.

Read More

4 comments   |  

0
Rating
  |  

Developers, Operations | Continuous Integration, Hyperic, tc Server

Blog : Apache Tomcat 7.0.26 Released

posted by Stacey Schneider on February 22, 2012 10:48 AM

The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.26

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This release is primarily a bug fix release and includes numerous bug fixes compared to version 7.0.25. The notable bug fixes include:

  • Improved @HandlesTypes processing which no longer loads all classes on web application start.
  • Ensure that POST bodies are available for reply after FORM authentication when using the AJP connectors
  • Corrected a regression that broke annotation scanning for many use cases including web applications packaged as WARs and many embedded scenarios.

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.

Read More

0 comments   |  

0
Rating
  |  

Developers, Operations | Apache Tomcat 7

Blog : Using the Tomcat 7 JDBC Connection Pool in Production

posted by dmikusa on January 23, 2012 03:14 PM

One of the new features with Tomcat 7 is a replacement to the commons-dbcp connection pool. While the commons-dbcp connection pool works fine for small or low traffic applications, it is known to have problems in highly concurrent environments (think multi-core/multi-cpu).

Fortunately, this is where the JDBC Connection Pool excels. It is a completely new connection pool which has been written from the ground up, with a focus on highly concurrent environments and performance.

Given its focus on high concurrency and performance, many users are finding that the JDBC Connection Pool can be great for use in a production environment. This article will discuss the features and options which make using the JDBC Connection Pool a great choice.

The Basics

Getting started with the JDBC Connection Pool is very simple. It was purposefully designed as a drop-in replacement for commons-dbcp and as such, if you've ever used commons-dbcp you'll be immediately familiar with the configuration for the JDBC Connection Pool.

This means the most existing commons-dbcp users can switch to the JDBC Connection Pool by simply adding the following property to their configuration factory=”org.apache.tomcat.jdbc.pool.DataSourceFactory”.

What about the other commons-dbcp configuration options? You don't need to change them at all. Virtually all of the commons-dbcp configuration options are supported by the JDBC Connection Pool. Including but not limited to: testWhileIdle, testOnBorrow, testOnReturn, maxActive, minIdle, maxWait, initialSize, removeAbandoned, removeAbandonedTimeout and logAbandoned.

Read More

5 comments   |  

0
Rating
  |  

Operations | jdbc-pool, Apache Tomcat 7

Blog : Apache Tomcat 7.0.25 released

posted by Stacey Schneider on January 23, 2012 10:47 AM

The Apache Tomcat team announces the immediate availability of Apache Tomcat 7.0.25

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This release includes numerous bug fixes and several new features compared to version 7.0.23. The notable new features include:

  • Align the Servlet 3.0 implementation with the changes defined in the first maintenance release (also known as Rev. A.). See the JCP documentation for a detailed list of changes.
  • Add support for connectors to automatically select a free port to bind to. This is useful when embedding and for testing.
  • Update to Commons Pool 1.5.7, Commons Daemon 1.0.8 and Eclipse JDT compiler 3.7.1.

Read More

2 comments   |  

0
Rating
  |  

Developers, Operations | Apache Tomcat 7

Syndicate content