Provider Implementations
To use JMS, one must have a JMS provider that can manage the sessions and queues. Starting from Java EE version 1.4, JMS provider has to be contained in all Java EE application servers. This can be implemented using the message inflow management of the Java EE Connector Architecture, which was first made available in that version.
The following is a list of JMS providers:
- Apache ActiveMQ
- BEA Weblogic (part of the Fusion Middleware suite) and Oracle AQ from Oracle
- EMS from TIBCO
- FFMQ, GNU LGPL licensed
- JBoss Messaging and HornetQ from JBoss
- JORAM, from the OW2 Consortium
- Open Message Queue, from Sun Microsystems
- OpenJMS, from The OpenJMS Group
- RabbitMQ, using AMQP
- Solace JMS from Solace Systems
- SonicMQ from Progress Software
- StormMQ, using AMQP
- SwiftMQ
- Tervela
- Ultra Messaging from 29 West (acquired by Informatica)
- webMethods from Software AG
- WebSphere Application Server from IBM, which provides an inbuilt default messaging provider known as the Service Integration Bus (SIBus), or which can connect to WebSphere MQ as a JMS provider
- WebSphere MQ (formerly MQSeries) from IBM
A historical comparison matrix of JMS providers from 2005 is available at http://www.theserverside.com/reviews/matrix.tss
Read more about this topic: Java Message Service
Famous quotes containing the word provider:
“That is the thankless position of the father in the family—the provider for all, and the enemy of all.”
—J. August Strindberg (1849–1912)