What Java Message Service Implementation?

Posted by Cliff on Wednesday February 27, 2002 @11:01AM from the choosing-the-right-framework dept.

alapalaya queries: "If you had to implement a message dispatcher with soft real time requirements, which has to manage a lot of messages, and in general subject to a lot of problematic requirements (including object persistence); all implemented using a Java Message Service; what implementation would you use? In fewer words: in your opinion what is the best Java Message Service Implementation? Among the various JMS implementations I am currently using SonicMQ; but it doesn't seem to scale up in a proper way (to around several hundreds of clients generating from 10 to 200 messages/sec each). What do you know about other vendors/implementations?"

1 of 25 comments (clear)

Min score:

Reason:

Sort:

What I Use by Anonymous Coward · 2002-02-27 11:10 · Score: -1, Troll

Here at my shop we use Xalan-J 2.3.1 (newly released), Xerces 2.0.0 (included with Xalan-J 2.3.1), Apache Tomcat 4.0.1, and Apache httpd 1.3.23 (and we're testing out version 2.0.x).

Thank you Apache for the implementation of XML standards processing in Java!