Well, this is a little embarrassing.
Only a few hours after we released 2.0.2, the JRuby guys released JRuby-22.214.171.124 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.
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 126.96.36.199
- [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