Red Hat
May 7, 2013
by The Entire TorqueBox Team

We're thrilled to announce the release of TorqueBox 2.3.1! This is a small update to TorqueBox 2.3.0 to fix a few outstanding bugs while we continue the main development work for the upcoming TorqueBox 3.0 series.

This release was delayed a couple of weeks from the original schedule because of a new addition to the TorqueBox team. Connor Benjamin Browning joins us after spending 9 months in a startup before things went belly-up. He'll be fulfilling the role of release manager and be the primary driver of schedules while my wife and I handle the change control duties.

What is TorqueBox?

TorqueBox is a Ruby application server built on JBoss AS7 and JRuby. In addition to being one of the fastest Ruby servers around, it supports Rack-based web frameworks, and provides simple Ruby interfaces to standard JavaEE services, including scheduled jobs, caching, messaging, and services.

Highlights of changes

  • The bundled JRuby version has been updated from 1.7.2 to 1.7.3.

  • A rather large memory leak in development mode when using Rails 3.2 and message processors or scheduled jobs has been fixed.

  • Several race conditions around booting applications with multiple services, multiple jobs, or booting TorqueBox with multiple applications deployed have been fixed. If you experienced intermittent failure of applications to deploy this should fix those issues.

  • Stomplets can once again access HTTP session data.

Scroll down for the complete list of issues fixed in this release.

Where's the torquebox-server gem?

Unfortunately, we found out at the last-minute after pushing all other TorqueBox 2.3.1 gems that the torquebox-server gem is too large to upload to It was not too large in the past and has not grown in size but has undergone a lot of changes in the last few months and one of those is apparently a decreased maximum gem size. We'll try to figure something out for future TorqueBox releases.


We've created a custom gem repository you can add as a source to get torquebox-server 2.3.1 - here's an example Gemfile.

source ''
      source ''
      gem 'torquebox-server', '2.3.1'

Upgrading from 2.3.0

Upgrading from 2.3.0 to 2.3.1 should be very straightforward, unless you use the torquebox-server gem - we worked hard to ensure only bug fixes made it into this release so no configuration or code should need changing.

Don't be a stranger!

As always, if you have any questions about or issues with TorqueBox, please get in touch.

Issues resolved since 2.3.0

  • [TORQUE-1012] - Eager loading for messaging is not working with ruby DSL and a shared pool
  • [TORQUE-1020] - rake torquebox:archive fails on Windows
  • [TORQUE-1028] - Session data is not available in Stomplets
  • [TORQUE-1029] - Memory leak in MessageProcessor with Rails development mode
  • [TORQUE-1031] - Web contexts should be normalized
  • [TORQUE-1036] - An app requiring an incremental configured with torquebox.rb crashes at deployment
  • [TORQUE-1037] - Update to JRuby 1.7.3
  • [TORQUE-1049] - Constant Foo not defined for Object errors when starting multiple services in Rails applications
  • [TORQUE-1055] - Improper use of StartContext.asynchronous() and .execute() can starve MSC threads
  • [TORQUE-1057] - Race condition in ScheduledJob can cause NPE on start
  • [TORQUE-1058] - Applications with multiple Services sometimes fail to boot
  • [TORQUE-1078] - ArrayIndexOutOfBoundsException during startup
  • [TORQUE-1081] - TorqueBox Stomp rack handler breaks on Ruby 1.9 because it does not follow the Rack spec
Original Post