About JRugged

The JRugged library implements some common patterns needed for building robust, production-ready server code in Java. It provides straightforward add-ons to existing code to make it more tolerant of failures and easier to manage. In other words, it makes your Java code more rugged!

Getting started is easy, just check out our Examples page. If you would just like to browse the wiki you can start on our Wiki Main Page

News

19 September 2011: Version 3.0.0 of the JRugged Library released!

• Fixed  issue #35 : Cleaned up and added Java Doc where it was missing
• Fixed  issue #37 : Fixed an NPE in PerformanceMonitor
• Fixed  issue #38 : NPE from DefaultFailureInterpreter (synchronization issue)
• Enhancement  issue #40 : Allows a CircuitBreaker to start/initialize in a hard trip state.
• Enhancement  issue #41 : Provide an exception mapper patter for the ConstantFlowRegulator
• Fixed  issue #42 : Compilation error due to log4j dependency
• Enhancement  issue #43 : The annotations available in the aspects package can now make use of the beans for PerformanceMonitors and CircuitBreakers allowing for a much cleaner implementation. The annotations are now much more useful and robust.
• Enhancement  issue #44 : RolledUpStatus was improved to allow a more concise status reporting. The naming of the classes associated with the status have changed as well - to improve the readability and understandability of the code base.
• Enhancement  issue #45 : Changed the pom's to include a more recent version of Spring (3.0.5)
• Enhancement  issue #46 : Added a way in the spring integration to automatically 'discover' those classes with the annotations included in the aspects package to auto-publish their JMX information if there is a JMX server already registered in the spring config.

Many thanks to walter_eggert at comcast dot com, coby_young at comcast dot com, raghushankar_ramalingam at comcast dot com and michajlo_matijkiw at comcast dot com (Mishu) who contributed to this next great release of the JRugged Library.

01 April 2011: Version 2.4.0 of the JRugged Library released!

• Fixed  issue #30 : 2.3.0 didn't compile from source cleanly
• Fixed  issue #34 : NPE in SampledQuartile
• Fixed  issue #36 : Method list had to have a comma in it to parse correctly
• Added support for monitoring performance of HTTP calls to multiple hosts
• Added a method for threading multiple service wrappers together in a chain

12 Feb 2011: Version 2.3.0 of the JRugged library released!

• Instances of CircuitBreaker now remember the last exception that tripped them
• Monitorable items can now have names
• Spring configuration has been enhanced providing for a JRugged namespace in the spring configuration
• Added plugin information for integrating JRugged with Hyperic monitoring
• A new spring heartbeat controller has been added allowing users to add simple health checks to their application via URL
• Improved Documentation on the projects wiki site for a variety of items
• Cleaned up project dependency list
• Added a new ability to Retry failed calls
• Added a new ability to rate limit calls to a service
• Added percentile/quartile measurements to PerformanceMonitor.
• Added a CircuitBreaker FailureInterpreter that fails based on percentage of errors per unit time rather then a count of errors per unit time.

Many thanks to david_mays at comcast dot com, anshu.mishra at gmail dot com, robert_bender at comcast dot com, jonathan_moore at comcast dot com who contributed to this next great release of the JRugged Library. Latest Stable Release: jrugged-core-3.0.0.jar, jrugged-aspects-3.0.0.jar, jrugged-spring-3.0.0.jar, jrugged-httpclient-3.0.0.jar