JBoss Messaging - Open Source Java Messaging from Red Hat
Introduction
JBoss Messaging enables high performance, clustered messaging for Java
JBoss Messaging 1.x is the default JMS provider in JBoss Enterprise Application Platform and JBoss SOA Platform and JBoss Application Server version 5.x
JBoss Messaging 2.0 boasts an all new architecture and superb performance. The current latest release of JBoss Messaging 2.0 is beta 1.
The goal of JBoss Messaging 2.0 is simple and uncompromising; to bring unrivalled levels of performance and reliability to messaging, and to be the fastest, best featured and most scalable multi-protocol messaging system. Why use JBoss Messaging 2.0? Here are just a few of the reasons:
- 100% open source software.
- Written in Java. Runs on any platform with a J2SE 5.0 JDK, that's everything from Windows desktops to IBM mainframes.
- Superb performance. Our class beating high performance journal provides persistent messaging performance at rates normally seen for non persistent messaging, our non persistent messaging performance rocks the boat too.
- Full feature set. All the features you'd expect in any serious messaging system, and others you won't find anywhere else.
- Elegant POJO based design with minimal third party dependencies. Run JBoss Messaging stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product.
- Seamless high availabilty. We provide server replication and completely transparent client failover so you don't have to worry about coding your client specially for an HA environment.
- Hugely flexible clustering. Create clusters of servers that know how to load balance messages. Link geographically distributed clusters over unreliable connections to form a global network. Configure routing of messages in a highly flexible way.
Here are some useful links
JIRAThe design forum for discussion of technical design issues can be found here
The user forum for discussion of user issues can be found here
Permanent development team
Tim Fox (Project Lead), Jeff Mesnil (Core Developer), Clebert Suconic (Core Developer), Andy Taylor (Core Developer)
|