Non other then JBoss Messaging provider is out there is market which gives an open source and standards-based messaging platform that brings enterprise-class messaging to the mass market. JBoss Messaging gives us a high performance, robust messaging core that is designed to support the largest and most heavily utilized SOAs, enterprise service buses (ESBs) and other integration needs ranging from the simplest to the highest demand networks and that’s not all JBoss Messaging also includes a JMS front-end to deliver messaging in a standards-based format and with JBoss Messaging core is also designed to be able to support other messaging protocols in the future.
JBoss Messaging also offers improvements then its earlier versions of it to performance in both single node and clustered environments, and features a modular architecture so that we can easily add more features in the future. The large and vibrant JEMS developer community fosters its continued innovation and enterprise quality. JBoss Messaging enables more agile applications in a wide range of scenarios from simple messaging needs to an enterprise-wide messaging foundation.
Things you get when using JBoss Messaging
- You get a strong focus on performance, reliability and scalability with high throughput and low latency.
- It gives you a foundation for JBoss ESB for SOA initiatives, by default JBoss ESB uses JBoss Messaging.
- It includes Topic (i.e publish-subscribe) and Queue (i.e. point-to-point) messaging models.
- It has persistent and non-persistent messages.
- Has a wide range of support for most major databases, including Oracle, DB2, Sybase, Microsoft SQL Server, PostgreSQL and MySQL.
- Will guaranteed message delivery that ensures messages arrive once and only once where required by using JBoss Messaging Bridge.
- Has a transactional and reliable interface which supports ACID semantics. It has complete integration with JBoss Transactions (previously Arjuna JTA) to support full transaction recovery.
- Would also give you a customizable JAAS-based security framework.
- Gives you an extensive JMX management interface.
- You can configurable Dead Letter Queues (DLQs) and Expiry Queues which really helps you in production environment.
- It has an automatic paging of messages to storage, which lets you use very large queues that would be too large to fit entirely within system memory.
- Like all other messaging providers it also has a strict message ordering which results in messages belonging to a particular message group being delivered according to the order of their arrival at the target queue.
- And lots more…
By default JBoss Messaging is the JMS provider in JBoss Enterprise Application Platform 4.3 and 5, however with upcoming new releases like EAP 6 (also in JBoss AS 7) would be having HornetQ as its JMS provider which would surely put the buzz in messaging. Do have a look at the below video which would give you an idea of HornetQ
Some reference documents which you can refer
- To know about JBoss Messaging on AS 5
- To know about HornetQ
- To go through various discussions on JBoss Messaging in JBoss
- To go through the discussions on various HornetQ/JBoss AS7 related discussions
- To know how to be always updated on JBoss World
Particle examples for Weblogic to JBoss Migration
Below are some particle examples which would surely help you guys to migrate your JMS setup from weblogic to JBoss configuration.
- Creating a Queue
- Creating a Topic
- Creating a Remote Queue
- Creating a Dead Letter Queue
- Creating a Expiry Queue
- Creating a Messaging Bridge
- Creating EJB3 MDBs listening to a queue on IBM Websphere MQ 7
All the things which can be done in Weblogic can also be done on JBoss Messaging as well, hence stay tune as lot more are coming soon….