In an at­tempt to 'in­crease per­for­mance', many peo­ple will try to hack around in JMS - there­by falling into the idem­po­tent re­ceiv­er trap by check­ing for du­pli­cate mes­sage re­ceipt. The con­se­quence: scal­a­bil­i­ty ac­tu­al­ly de­grades!

For­tu­nate­ly, the best way to en­joy re­li­able mes­sag­ing is also the sim­plest one, and it scales lin­ear­ly.

We've up­loaded a slideshare pre­sen­ta­tion on de­vel­op­ing trans­ac­tion­al ap­pli­ca­tions with Spring. En­joy!

Here is an­oth­er ex­cel­lent ar­ti­cle about the cost of ap­pli­ca­tion servers, and why a par­a­digm shift is need­ed with lighter-weight al­ter­na­tives:

http://www.tom­ca­t­ex­pert.com/blog/2010/06/03/mi­grat­ing-jee-ap­pli­ca­tions-tom­cat-mo­ti­va­tion-mi­grat­ing

In­ter­est­ing note: the au­thor used to work at Bea, so he def­i­nite­ly knows what he is talk­ing about;-)

Check out http://www.tom­ca­t­ex­pert.com/blog/2010/07/07/how-mi­grate-jee-ap­pli­ca­tions-tom­cat for a nice dis­cus­sion on how to mi­grate from jee to a light-weight al­ter­na­tive like Tom­cat - with Atomikos for JTA if need­ed.

Check out this cool blog en­try on how this can all work to­geth­er.

DISCLAIMER: the sug­gest­ed so­lu­tion has not yet been ver­i­fied by Atomikos...

2018 UPDATE: the link seems to be bro­ken by now - apolo­gies for that.