Red Hat
Aug 8, 2011
by The Entire TorqueBox Team

TorqueBox v1.1.1 Released

The entire TorqueBox team is proud to announce immediate availability of TorqueBox v1.1.1.

What is TorqueBox?

TorqueBox builds upon the JBoss AS Java application server, mixing in JRuby, to provide a scalable platform for Ruby applications, including support for Rails, Sinatra and other Rack-based frameworks.

In addition to supporting popular web frameworks, TorqueBox bridges many common Java facilities provided by JBoss, including scheduled jobs, caching, messaging, and services.

What's in this release?

This is a bug-fix release, and includes a few notable changes:

  • JRuby 1.6.3 has an issue that may cause TorqueBox to crash when an app is deployed (see JRUBY-5933 for the specifics). This release includes a workaround to prevent that from happening. This issue currently affects TorqueBox 1.1.

  • We made a small change to the way we initialize JRuby runtimes for Rails applications, resulting in a ~30% improvement in the runtime startup time.

  • Improved support for Rails 3.1. Rails 3.1 is in the release candidate stage (currently rc5), and often has significant changes between candidates. As such, we may need to make another TorqueBox release when Rails 3.1 final is released to track additional changes there.

Tested Frameworks

With each release of TorqueBox, we test with a specific set of frameworks and libraries, and recommend their use with that release. For the 1.1.1 release, we have tested against:

  • JRuby 1.6.3
  • rack 1.1.0
  • rails 2.3.11
  • rails 3.0.5
  • rails 3.1.0.rc5
  • activerecord-jdbc-adapter 1.1.3
  • sinatra 1.2.3

Community Contributions

This release includes several fixes and documentation contributions from the following community members:

Thanks so much for your contributions!

What's changed since 1.1?

  • [TORQUE-492] - Globbing doesn't translate multiple single splats correctly
  • [TORQUE-493] - Assets contained in the app/assets fail to serve in Rails 3.1
  • [TORQUE-497] - TorqueBox seg faults with 'invalid memory access' or 'malloc double free' when initializing runtimes
  • [TORQUE-499] - Rails Initialization Wastes Several Seconds Inspecting Caller Stacks
  • [TORQUE-503] - Unable to load bundled gems due to wrong vfs paths
  • [TORQUE-506] - should only try to mount jars in JRUBY_HOME
  • [TORQUE-516] - Update docs to mention the -b requirement for clustering
  • [TORQUE-519] - activerecord-jdbc-adapter 1.1.3 fails when used with vfs sqlite path
  • [TORQUE-522] - Update rails template to not include gems that will be automatically included in the Gemfile by rails 3.1

What's next?

After the last release, we stated that we didn't anticipate any more 1.x releases before 2.x, but that is clearly not the case. Expect no more sweeping proclamations of that nature.

The 2.0 release will be built on top of the recently released JBossAS 7, and have a considerably faster deploy time along with a much lower memory footprint. We hope to have a 2.0 beta soon, but in the meantime, feel free to give our incremental builds a try.

Original Post