Comments about O'Reilly Media Java Message Service:

I had read Sun's information on JMS and I worked through their examples. After writing my own test programs, I only achieved 100 messages per second through Sun's J2EE server. I searched the web for something to tell me whether IBM or BEA's websphere products provided faster message handling. Our product is a Stock Market live data feed. Our J2SE API gets us 3000 msgs/sec through TCP/IP, so 100 msgs per second is not feasable.

So, about the book. I had hoped to find suggestions as to how to optimize JMS throughput. Chapter 7, "Deployment Considerations" should have provided some help. It asked more questions than it answered and offered no specific solutions. Overall, I got a little more out of the book than I did reading Sun's Java site and tutorial.

If you have any suggestions, please send me email at [...].

If its flame mail, please send it to [...]

Comments about O'Reilly Media Java Message Service:

Very nice book

its really help full for me in learning JMS.Thanx a lot to users but there is some confusion in printing i.e if you take Fig:6-1 and 6-2 6 the action is missed in 6-1 and 3rd action is missed in 6.2 but these are allneglegible. but for a person who is starting his JMS might lead wrong indications.

Great work my friends

Comments about O'Reilly Media Java Message Service:

This is the great book for "java message service".it's very easy to read this book.and author had written in such a way that any body having java basics can under stand easily.what's happening with jms.it's very intresting to read first intro chapters.all chapters are well oganized.

finally a very good book for jms.good work donr by authors.

Comments about O'Reilly Media Java Message Service:

I've been involved with developing distributed applications, mostly in java, for a few years now and until really becoming aware of the JMS, I was stuck with writing exotic protocols and worrying about the Socket layer of the application. While this is highly educational, it isn't the best way to do things when you have to get The Job done.

I was introduced to JMS and MOM via xmlBlaster, and was thrilled to death when I came across this book. I was at first a little nervous about the book because of its, what I deemed lack of, pages. But after diving into it, and reading it straight through I found that the authors ability to provide clarity meant that hundreds of pages were not needed.

This book also managed to clear up several nagging deficiencies I had with JNDI and how the whole messaging queue design works. This book should be required for anyone who is charged with designing, building and testing any type of legacy integration, messaging or distributed application project. The clear and exacting descriptions of the technologies and the real-world examples provide us readers with something we can actually see and play with (I love writing chat applications!)

I believe that this book has a shot at becoming a "bible" of sorts for those of us who write distributed apps using java. Excellent work.

Comments about O'Reilly Media Java Message Service:

Excellent coverage of the JMS 1.02 API. While I was a bit surprised at the order of coverage (e.g. covering publish-subscribe first, rather than point-to-point messaging) it makes a great deal of sense when you consider someone approaching the topic who may not be familiar with existing messaging systems.

I loved the approach of presenting a complete working example first, and then describing the pieces in order. This makes for an exceptionally clear and lucid presentation of the parts of the JMS API. I also found the coverage of the different JMS products to be fair, accurate and even-handed. Finally, I was gratified to find a section on handling exceptional conditions and failures when using JMS -- something that is sorely missing from most shorter discussions of the topic.

Overall, it's a great introduction to JMS for those unfamiliar with messaging, and a handy reference and guide to the API for those of us more familiar with the topic. It should occupy a prominent place on any J2EE Architect's bookshelf.

Kyle Brown

Executive Java Architect

IBM WebSphere Services