Skip to main content

HOWTO: Parallel deployment on tomcat 7

News broke out recently that Tomcat 7 supports parallel deployment.

This feature allows one to deploy a newer version of a web application while maintaining the current one online. The net effect is that new users will be connected to the newest version while already connected users will not be kicked out. Neat uh?
One could even have more than two versions online at any time (if that was necessary).

The details of how this works are explained in the Context Container documentation. Only it doesn't really tell you how to use it, it tells you how they implemented instead.

So what do you have to do to take advantage of this great feature?

First of all upgrade to Tomcat 7 (which btw requires Java 6), but you knew that already, didn't you?

Then simply adopt the following naming strategy when deploying apps: name your war file mygreatapp##version.war (note the ## used to mark the beginnning of the version substring) where version can actually be anything (it is mapped to a String property) but to be safe I suggest using a zero-padded always increasing numeric value (your SVN revision number, perhaps).
Example:

mygreatapp##0001.war

That's it. No configuration, rebuilding or trick hats required.

Note: previous app versions will NOT be removed automatically. You will have to remove them yourself using the manager app when their session count drops to zero or you just can't wait anynmore.

Note2: the app version is visible in the manager app, in a dedicated column right beside path.

Note3: if you plan to use a String for the version make sure that the newer version values are greater (in String terms) than previous ones or you'll end up with new users connecting to an older version of the app instead. That's what zero padding is for.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post.
Btw: the recovery, depending on db size and disk speed, is going to take long.

The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux.

The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking.

Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd into the mirth home. …