The Jakarta Project
      The Apache Jakarta Tomcat Connector

The Apache Jakarta Tomcat Connector

Changelog

Preface

This is the Changelog for Jakarta Tomcat Connectors. This changelog does not contain all updates and fixes to the Tomcat connectors (yet). It should contain fixes made only after November 10th 2004, when the new documentation project for JK has been started.

Changes from JK 1.2.7

Native
update 32317: Making mod_jk replication aware (Clustering Support). Patch provided by Rainer Jung. (mturk).
fix 31132: Core dump when JkLogFile is missing from conf. (mturk)
Changes from JK 1.2.6

Native
update Added new property named recover_time that can be used to change the default 60 second recover time. (mturk)
update Added custom retries for worker, so we don't depend on default setting. If set to a number grater then 3, it will sleep for 100ms on retry greater then 3 and then try again. (mturk)
update Added JkWorkerProperty directive that enables omiting workers.properties file. For example: JkWorkerProperty worker.ajp13a.port=8009. (mturk)
fix Check all JSESSIONID cookies for a valid jvmRoute. If you have multiple Tomcats with overlapping domains, then you can get multiple cookies without a defined order. This will route correctly as long as the different domains don't have any Tomcats in common. (billbarker)
update Added JkUnMount directive for negative mappings that works as opposite to JkMount directives. It is used for blocking of particular URL or content type. (mturk)
update Added wildchar match uri mappings. One can now use JkMount to map /app/*/servlet/* or /app?/*/*.jsp. (mturk)
update Rewrite the logging by adding Trace options. (mturk)
update Added socket_timeout property that sets the timeout for the socket itself. (mturk)
fix Changed socket_timeout property to recycle_timeout. This better explains what the directive actually does. (mturk)
fix Changed the load balancer algorithm. The idea behind this new scheduler is the following: lbfactor is how much we expect this worker to work, or the worker's work quota. lbstatus is how urgent this worker has to work to fulfill its quota of work. We distribute each worker's work quota to the worker, and then look which of them needs to work most urgently (biggest lbstatus). This worker is then selected for work, and its lbstatus reduced by the total work quota we distributed to all workers. Thus the sum of all lbstatus does not change.(*) If some workers are disabled, the others will still be scheduled correctly. (mturk)
JK 2

JK2 has been put in maintainer mode and no further development will take place. The reason for shutting down JK2 development was the lack of developers interest. Other reason was lack of users interest in adopting JK2, caused by configuration complexity when compared to JK.


Copyright © 1999-2004, Apache Software Foundation