Thursday, 25 November 2010

Infinispan 4.2.0.CR2 "Ursus" is out!


CR2 release fixes a critical issue from CR1: NumberFormatException when creating a new GlobalConfiguration objects (ISPN-797). Besides this, the client-server following two issues were fixed around client server modules:
- In Memcached, negative items sizes in set/add should return CLIENT_ERROR (ISPN-784)
- In REST, HEAD on nonexistent cache still produces status 500 (ISPN-795)
Big thanks to Galder for fixing these so quickly!


Wednesday, 24 November 2010

Infinispan 4.2.0.CR1 "Ursus" is out!


4.2.CR1 code name "Ursus" has just been released! It contains multiple fixes and improvements, mainly on memcached server and rehashing when cluster topology changes. The jgroups version was also upgraded to 2.11. Another thing that's worth mentioning is that the default port for HotRod server has changed from 11311 to 11222 (here's why).
You can download it from here. Please share your thoughts with us!


Tuesday, 9 November 2010

Infinispan Community Meetup @ Devoxx 2010

Infinispan and Seam are doing it again, and this year Arquillian will be there to keep things in check: a community social in the midst of Europe's premier Java conference, Devoxx in Antwerp. If you plan to be at Devoxx - or just happen to be nearby - and fancy an evening of in-depth conversation about three open source projects set to rock the enterprise, come on by and partake in some of the finest beer in the world with the project core developers. Demos, design discussions, architectural questions are all fair game. Join our pilgrimage to Kulminator at 20:00 on Monday the 15th of November (near the Groenplaats Station).

And a quick note, just because open source is all about Free as in Speech doesn't mean we can't have free beer. Yes, we're sponsoring beer as well as other project-related goodies, but these are limited, first come first served.

Where: Kulminator, close to Groenplaats Station, Antwerp
When: Monday the 15th of November, 2010
What time: 20:00

View Larger Map

Hope to see many of you there!


Thursday, 4 November 2010

Infinispan likes GitHub

It had to happen someday - Infinispan's primary source code repository has now moved to GitHub.  We have abandoned Subversion as a version control tool for the far superior distributed VCS which has found favour in many large and complex open source projects.  I've been experimenting with a GitHub setup for the past few weeks, with a snapshot of the Infinispan repository, and git is a sheer joy to use - a sublime experience, once you get your head around the concepts of distributed version control.  GitHub makes things even sweeter, with an awesome web based UI.

Anyway, a quick summary:
  • Infinispan sources are no longer in Subversion, on
  • The primary repository for Infinispan is now
    • Clone this repository at will!
    • Contributions should take the form of pull requests on GitHub
  • Infinispan's Hudson, release tooling and other systems have been updated to reflect this change
For those used to working with Infinispan's Subversion-based setup, or those new to git, I've put together a short wiki page on getting started with Infinispan on GitHub.

Oh, and I'd love to hear your feedback on this move.

Happy cloning!

BETA is out!!

I've just released the long-awaited first beta of Infinispan 4.2.0, codenamed Ursus.  The blocker that's been keeping Ursus in Alpha for so long - ISPN-180 - is now complete and ready for you to take out for a spin.  Thanks to the work put in by Mircea and Vladimir, ISPN-180 adds support in the distribution algorithm to detect whether Infinispan instances are co-located on the same physical server (or even the same rack) and pick secondary owners of data with this knowledge in mind. This helps ensure maximum durability of data, so if physical machines - or even an entire rack - were to fail, data is not lost.  For more details on ISPN-180, have a look at this wiki page which details its use.

The JOPR/RHQ plugin now works in multi cache manager environments (ISPN-675) and thanks to ISPN-754, cache manager instances can be easily identified when using the JOPR/RHQ management GUI.  As a result of ISPN-754, JMX object names follow best practices as set up by Sun/Oracle and so this means that object names exported to JMX have changed from this version onwards. See this wiki page for detailed information.

For a list of all fixes since Alpha5, have a look at the release notes in JIRA, and as always, download the release here, and let us know what you think using the user forums.

Onward to release candidate and final release phases!  :-)