Well, this is a little embarrassing.

Only a few hours after we released 2.0.2, the JRuby guys released JRuby-1.6.7.2 fixing a security issue. Along with having found a few of our own bugs in the past 4 days, we are embarrassingly proud to announce the availability of TorqueBox 2.0.3.

Happy Cuatro de Mayo!

• Download TorqueBox 2.0.3 (ZIP)
• Browse HTML manual
• Browse JavaDocs
• Browse Gem RDocs
• Download PDF manual
• Download ePub manual

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.

JRuby 1.6.7.2

The only change incorporated into the upgrade of JRuby is the updating of the bundled RubyGems to 1.8.24. This version starts checking the server certificate of rubygems.org. That's a good thing.

public/ directory not consistently serving assets

You might've noticed that files from your public/ directory were only being served every other request or so. This has been tracked (via TORQUE-810) and fixed in 2.0.3.

Keep up with the flurry of releases

As always, one of the best ways to keep up with the flurry of releases and announcements about TorqueBox is to follow us on Twitter (@torquebox).

Issues resolved since 2.0.2

• [TORQUE-791] - Web context in torquebox.rb is ignored during deployment
• [TORQUE-810] - Files & Assets in Rails /public folder are only served successfully 50% of the time and are sometimes incorrectly passed to rails
• [TORQUE-813] - undefined method `__enable_backgroundable_newrelic_tracing'
• [TORQUE-814] - Upgrade to JRuby 1.6.7.2
• [TORQUE-816] - Capistrano app_environment produces an invalid deployment descriptor
• [TORQUE-818] - Services docs incorrectly state that app/services/ has to be added to the load path

We're as happy as kids around a maypole on May Day to announce the immediate availability of TorqueBox v2.0.2. This release brings JRuby 1.7 compatibility, fixes for distributed transactions on Oracle, several other minor bug fixes, and some changes and additions to our documentation - including oft-requested explanations about how logging works, thanks to jcrossley3.

• Download TorqueBox 2.0.2 (ZIP)
• Browse HTML manual
• Browse JavaDocs
• Browse Gem RDocs
• Download PDF manual
• Download ePub manual

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.

JRuby 1.7 Compatibility

We've tested TorqueBox with recent builds of JRuby's master branch to ensure it is compatible with the upcoming 1.7 release. Note that we're still bundling JRuby 1.6.7 and building TorqueBox against JRuby 1.6.7 so you'll need to bring your own JRuby 1.7. You'll also see a warning logged like "WARNING: TorqueBox was built and tested with JRuby 1.6.7 and you are running JRuby 1.7.0.dev". Once JRuby 1.7 is released we should be able to remove that warning.

Updates on the Release Process and Versions

The 2.0.x TorqueBox releases will be bugfixes only from this point forward, while we'll continue adding new features to what will become 2.1.0. The goal is to ensure maximum stability of all future 2.0.x releases while not hindering new feature requests and development.

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.0.1

• [TORQUE-567] - Get XA transactions working on Oracle
• [TORQUE-570] - Occasional deployment failures when redeploying app
• [TORQUE-753] - Integrate rack-webconsole or something like it with BackStage
• [TORQUE-762] - oracle_enhanced errors with No suitable driver found for jdbc:oracle:thin
• [TORQUE-775] - Make TorqueBox Compatible with JRuby 1.7
• [TORQUE-777] - Document How to Connect VisualVM to a Remote TorqueBox
• [TORQUE-778] - Document New Relic integration
• [TORQUE-780] - Newrelic Doesn't work on 2.0.0 or 2.0.1
• [TORQUE-781] - Don't Assume Every ActiveRecord User is Using ActiveRecord-JDBC
• [TORQUE-783] - Clustering Without Multicast Docs Should Show ModCluster Example
• [TORQUE-784] - HornetQ fails to cluster on some platforms
• [TORQUE-787] - Some bug in STOMP makes it use all CPU resource
• [TORQUE-792] - Torquebox not passing HTTP OPTIONS requests through to our app
• [TORQUE-794] - Allow to check if curent Ruby runtime is a web context, a message processor or a service.

Image © Copyright Jim Champion and licensed for reuse under this Creative Commons License. The original can be be found here.

Hot on the heels of our 2.0.0 release, we're happy as a Sunday in Paris, full of song, dance, and laughter to announce the immediate availability of TorqueBox v2.0.1. This fixes a couple of regressions that slipped in between cr1 and the 2.0.0 final release, as well as a few bugs that didn't surface in the beta/candidate cycle.

• Download TorqueBox 2.0.1 (ZIP)
• Browse HTML manual
• Browse JavaDocs
• Browse Gem RDocs
• Download PDF manual
• Download ePub manual

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.

What's changed since 2.0.0?

There aren't that many fixes in 2.0.1, but a couple of them are important, and warranted a release sooner rather than later:

• Clustering behind mod_cluster was broken in 2.0.0, but now works like gangbusters!
• Our capistrano tasks had an issue where it would appear to redeploy an application, but actually failed to do so.

Other notable changes in this release include:

• We've changed the way HornetQ buffers messages for processors to improve their utilization when your processor concurrency is > 1 and the processors are performing time consuming operations. If you are using the default concurrency of 1, you should see no performance change.
• You can now properly connect to a remote topic or queue running in another TorqueBox container.
• TorqueBox now properly starts up if used under domain mode.

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.0.0

• [TORQUE-748] - the default consumer-window-size may be a poor default
• [TORQUE-755] - mod_cluster should be easier to setup
• [TORQUE-756] - Capistrano-based deploys break in MRI 1.9.3p125
• [TORQUE-757] - Capistrano no longer fully deploys
• [TORQUE-758] - Capistrano support should use deploy:create_symlink hook
• [TORQUE-759] - Debugger Doesn't Work When TorqueBox Started via 'torquebox run'
• [TORQUE-760] - Cannot get more than two backgroundables to run concurrently
• [TORQUE-761] - Rails template add_source line leftover from incremental builds
• [TORQUE-765] - TorqueBox should ship without the modcluster ROOT context excluded
• [TORQUE-766] - None of the scripts in jboss/bin/ are executable in the gem install
• [TORQUE-767] - Update the production setup guide to refer to 2.0.1 instead of cr1
• [TORQUE-769] - Cannot subscribe to remote HornetQ Topics from within a TorquBox application
• [TORQUE-771] - Don't Display "Can't get or create an Infinispan cache" Log Message When Running Rake / Rails Commands
• [TORQUE-773] - Domain mode missing dependency

The entire TorqueBox team is proud to announce the immediate availability of TorqueBox v2.0.0.

• Download TorqueBox 2.0.0 (ZIP)
• Browse HTML manual
• Browse JavaDocs
• Browse Gem RDocs
• Download PDF manual
• Download ePub manual

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.

What's special about 2.0.0?

This is the 2.0.0 final release, which is a major upgrade over TorqueBox 1.x. Notable inclusions in 2.0.0 include:

• JRuby 1.6.7 (with better Ruby 1.9 support)
• JBoss AS 7.1.1 (faster boot time, smaller memory footprint)
• Multi-resource distributed XA transactions
• WebSockets/STOMP
• Considerable speed & memory improvements over 1.x

What's changed since cr1?

We fixed a handful of issues reported against cr1, and gave our documentation an overhaul. Highlights in this release include:

• A brand-spankin-new production setup guide
• A chapter in the documentation covering application deployment
• Jobs & Services are now singleton by default - if you are running in a cluster and were relying on Jobs and Services running on every node by default, you'll need to turn off singleton support by setting singleton: false for each Job or Service.

How do I migrate from 1.x to 2.0.0?

The biggest changes you'll see will be around any xml configuration changes you have made to the underlying JBoss AS server. TorqueBox 1.x was based on AS6, and 2.x is based on AS7, which is considerably different than AS6. Any changes you'll need to make to your application code and configuration should be minimal, if any. We plan on writing migration guide sometime in the next couple of weeks. In the meantime, read through the documentation, give it a try, and bug us if you have any questions or problems.

Thanks to an outstanding community

Thanks to everyone that helped us with patches, bug reports, and generally good natured support as we went through this major rewrite over the last 11 months. You guys are great! Without you, there would just be us :)

We'd especially like to thank the following folks for their code contributions to 2.0.0:

• Benjamin Anderson
• Bruno Oliveira
• Carl Hörberg
• Curtis Carter
• David Glassborow
• Gavin Stark
• Joe Kutner
• John Lynch
• Joshua Borton
• Kris Leech
• Marek Goldmann
• Mike Dobozy
• Robert Rasmussen
• Saulius Grigaitis
• Tony Collen
• penumbra
• tinylox

Issues resolved since cr1

• [TORQUE-190] - Create Documentation for Production setup of Torquebox
• [TORQUE-683] - Stomplets fails sometimes during setup
• [TORQUE-713] - TorqueBox documentation should highlight necessary postgres XA configuration changes
• [TORQUE-715] - torquebox upstart task does not properly kill standalone server when stopping the torquebox service
• [TORQUE-723] - jobs cannot load classes in a namespace
• [TORQUE-725] - Document new torquebox run options
• [TORQUE-726] - by default the Gemfile does not specify the version of torquebox, which cause bundle to bring in 1.1.1 => causes errors at runtime
• [TORQUE-728] - Log a Warning and Disable XA When We Can't Parse database.yml
• [TORQUE-729] - injection analyzer fails at startup
• [TORQUE-730] - Default Xss is too small for medium-to-large Rails apps
• [TORQUE-731] - torquebox.rb DSL no longer forwards options to services
• [TORQUE-732] - Don't Automatically Attempt XA Connections to Non-Standard Database Keys in database.yml
• [TORQUE-733] - Limit Maximum Stack Depth During Injection Analysis
• [TORQUE-736] - Upgrade to AS 7.1.1.Final
• [TORQUE-737] - Rails template (for Rails 2.x, at least) should enable torquebox_store for non-session caching (Rails.cache)
• [TORQUE-738] - Torquebox/JBoss tries to deploy netty jar as application
• [TORQUE-739] - Component configuration involving arrays don't survive full transfer to components when using torquebox.rb DSL
• [TORQUE-743] - Write a basic config/torquebox.yml with some instructional comments as part of $TORQUEBOX_HOME/share/rails/template.rb
• [TORQUE-744] - Support torquebox_init.rb in both ROOT and ROOT/config
• [TORQUE-745] - TorqueBox Session (Section 4.4) Docs Should Show Session Usage for Rack Apps and Cross-Reference Rails / Sinatra Examples
• [TORQUE-746] - TorqueBox::Infinispan::Cache not using cluster, always local
• [TORQUE-747] - Change deploy:restart deploy:stop deploy:start behaviour
• [TORQUE-749] - Clustered Jobs/Services should be singleton by default
• [TORQUE-750] - Resource Injection is befuddled

On Sunday, March 25th Arun Agrawal and Rocky Jaiswal presented TorqueBox at RubyConf India. Judging by the reactions on Twitter, it looks like they did a great job of bringing some TorqueBox love to our Rubyists in India. Thanks guys!

Their slides are embedded below.