Sep
14
2004

Migrating from Tomcat to Jetty

I’ve been having ongoing hassles with Tomcat 5 on my 64Mb Linode – and it’s the only software on that box that’s been unreliable.

After getting sick of killing the thing off, I’ve made the jump to Jetty. It’s smaller, faster, and hopefully more robust. Configuration is a snack – once you workout that the XML format just mirrors the API calls it support. My subdomains are working just great, but now I just need to work out how to configure the root context. BTW Jetty starts in around 4 seconds. Nuff said.

Pebble even ships with instructions on how to configure Jetty for Pebble use.

And best of all, it’s a Aussie product. Aussie, Aussie, Aussie, Oi, Oi, Oi!!!

About the Author: Glen Smith

2 Comments + Add Comment

  • If your Linode was running on RH 9 (or something based on RH 9), you needed the usual LD_ASSUME_KERNEL=2.4.1 environment variable. Don’t know if that was your problem, but it’s quite likely. For the startup time issue, you can remove the admin webapp if you’re not using it.

  • Thanks dude. I’m actually running on very lean and mean Debian. I wasn’t aware of the env variable. Thanks for the tip.

    But I’ve gotta say Jetty runs *heaps* faster than Tomcat on this config. I’ll wait to see how long it stays up.

Leave a comment

Glen Smith

About Glen

Co-author Grails in Action