Back to website Login
There was a problem loading the comments.

Release Notes - mod_jk 1.2

Support Portal  »  Knowledgebase  »  Viewing Article
  Print

 

Overview - mod_jk 1.2

This Release Note covers all point releases for the mod_jk Apache Tomcat Connector that are offered by eApps. Upgrade instructions are included.

mod_jk 1.2 is available for all eApps servers using the ISPmanager Control Panel (CentOS 6 and CentOS 7). If you are on a CentOS 5 (Webmin) server and need mod_jk 1.2, you will need to migrate to an up to date server. Contact eApps Sales for more information.

eApps recommends, as a best practice, to maintain a staging server where you can test software upgrades before moving them into production. This approach will allow you to minimize the risk of data loss and downtime of your production service when performing software upgrades. If necessary, you can rebuild your staging Virtual Server on demand so that you have a fresh installation to test on. If you need more information about setting up a staging VM, please contact eApps Sales.

eApps Release Notes for mod_jk 1.2.42
eApps Release Notes for mod_jk 1.2.40

How to Upgrade
mod_jk 1.2.x to mod_jk 1.2.y (newer version)

Highlighted Features and Fixes in mod_jk 1.2.42

Features

  • Status: Add maximum number of open backend connections to status worker
  • Apache: Add debug logging for result of JkOptions configuration processing
  • Add more checks for shared memory allocation

Fixes

  • Status: Use numeric time stamps instead of textual ones to avoid non-well-formed XML output
  • Apache: Propagate errors reading the request body from the client to mod_jk so Tomcat sees an error rather than a truncated body
  • AJP: Forward name of SSL protocol used for handling the request (SSLv3, TLSv1, TLSv1.1, TLSv1.2)
  • ISAPI: Update bundled pcre from version 5.0 to 8.38
  • ISAPI: Align the make files for 32-bit and 64-bit builds
  • HTTPD: Avoid segmentation fault if mod_jk is configured with an invalid value for JkShmFile
  • Reduce log buffer from 8KB to 1KB

The Official Changelog for mod_jk 1.2.42 is available here - http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html

Highlighted Features and Fixes in mod_jk 1.2.40

Features

mod_jk 1.2.40 is a bug fix and security release, no new major features have been added

Fixes

  • Forwarding of chunked requests is fixed
  • Grammar fix in 503 error page
  • Removed quotes from quoted session cookies

The Official Changelog for mod_jk 1.2.40 is available here - http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html

How to Upgrade

It is your responsibility to ensure that your application will work on the newer version of mod_jk. There may be incompatibilities that will affect how your application works. Please make sure that you have read the official Release Notes and Changelog, and have done any necessary testing before upgrading a production application.

You should also make a backup of your application, your databases, your configuration, and any tunings or changes you have made. If you do not have current backups and something goes wrong during the upgrade process, you could have data loss.

To upgrade mod_jk, you will need to work from the command line using SSH, and you will need to be able to work as the root user. You will need to use yum to upgrade the application.

mod_jk 1.2.x to mod_jk 1.2.y (newer version)

Once you are logged in to the Virtual Server using SSH, do the following as the root user: yum update mod_jk. This will upgrade the application.

[root@eapps-example ]# yum update mod_jk

Share via
Did you find this article useful?  

Related Articles

On-Premise Help Desk Software by SupportPal

Categories

© Cloudscale365