The Apache Tomcat Connectors - News (1.2.50) - 2009 News and Status
Author: Apache Tomcat Connectors Project

## 2009 News and Status

### 2009 News & Status

#### 22 March - JK-1.2.28 released

The Apache Tomcat team is proud to announce the immediate availability of Tomcat Connectors 1.2.28. This is a stable release concentrating mainly on some bug fixes.

Please see the ChangeLog for a full list of changes.

If you find any bugs while using this release, please fill in the Bugzilla Bug Report.

The most important new features in this version are:

### Better Error Detection for Load Balancer Workers

Local and global error states have been improved. You can fine tune the behaviour with the new "error_escalation_time" attribute (see the timeouts documentation).

### Dynamic Address and Port Change Using the Status Worker

The status worker now allows you to change the address and the port of an AJP13 worker on the fly. You can e.g. provision dummy workers with a port equal to "0", which will be automatically put into stopped mode during startup. Later, when you want to actually use these workers, you set their address and port to the final values.

Note that already existing connections will go on using the old address and port. This will be improved in future versions.

### New Data in Status Worker Display

The status worker display now also contains the timestamp of the last worker errors.

### Improved Proxy Flexibility

You can now overwrite more request metadata before the request gets send to the backend. This is helpful in case there are other reverse proxies in front of your web server. A new documentation page explains this in detail.

### Improved IIS Support

IIS support has been improved especially when using mutltiple application pools. Furthermore you can now configure the ISAPI plugin to update the uriworkermap.properies file on a regular interval using the watchdog thread.

### JNI Worker Deprecation

Workers of type jni are broken since a long time. Since there is no more use for them, they have been deprecated now, and will be removed in a future release.