JMS seems to be the darling of the J2EE community and certainly holds tremendous potential for solving numerous distributed computing problems and for building loosely coupled systems. Everywhere you look it seems that JMS is plugged in as an important component of a distributed architectures.
I'm looking for input from the community regarding successful implementations in PRODUCTION based on JMS, and which vendor was selected. I would also like to have some input on the selection process, which vendors were considered, and the reasoning process.
It's one thing to play around with toy JMS examples, it's another thing to have it in production under heavy load, I'd really like to hear from those who have put JMS to the test.
I have encountered my share of poor implementations that could not be trusted either for lack of clusterability, poor performance, or instability. My situation is that I'm locked into Weblogic 5.1 for the time being and I'm hoping that the 6.1 implementation is all that it's cracked up to be. In the mean time I would like to consider other options. I have also chatted with several other shops that their selection of JMS as a core J2EE technology lead to a myriad of heartaches due to unstable implementations.
What's up with your JMS based project? Thanks in advance.
Bebop Software LLC