Java Tutorial - Java Scipt : JBossMQ

Java Tutorial - Java Scipt :

JBossMQ


JBossMQ is the JMS provider that is bundled with the JBoss J2EE application server. JBossMQ is a clean-room, pure-Java implementation of JMS. Formerly known as SpyderMQ, it was first released to the public in April 2000 and still enjoys high development activity. The following table gives a summary of JBossMQ.
One caveat about JBossMQ is that information on the Web site tends to lag behind the development, so the best place to go for the latest scoop is the forums.

The performance of JBossMQ is very good on a single machine, but it has issues scaling under heavy load. Clustering code is being tested at the time of this writing, which may prove to be a useful feature. The optimized invocation layer (OIL), which uses TCP/IP as the basis for the messaging protocol, has excellent performance. JBossMQ holds the performance edge over the other JMS providers when the load is manageable. There is also another messaging protocol, named UIL, that is supported by JBossMQ for cases where the JMS client is located behind a firewall. This is a nice bonus touch. JBossMQ seems to have a wide variety of protocol support,
like OpenJMS, but it fails to trumpet that fact. JBossMQ is compliant with JMS 1.1, the most recent version of the specification. It was one of the JMS providers to reach compliance, which is impressive. JBossMQ is used in production environments and has performed admirably in those scenarios. Support for transactions is optional in the specification but possibly critical to an enterprise application. JBossMQ includes transactional
support for messaging. As scalability features such as flow control and clustering are added, there is a risk that reliability of JBossMQ will suffer in the short term. Without a doubt, the JMX feature makes administration a breeze. Both extremely powerful and imminently accessible, JMX is the standard for Java administration. As products continue to add JMX support and generic tools arise for management of any JMX-enabled product, huge improvements in administration can be expected. For now, JBossMQ gets a big thumb’s up for its support of JMX. Because JBossMQ is integrated with the JBoss J2EE application server, integration is not a factor if you are using JBoss; right out of the box; you have a complete J2EE solution ready to run. Unfortunately, newer versions of
JBossMQ are only available for download as a part of the entire JBoss bundle. We will examine how to separate out JBossMQ for use with other J2EE application servers. Ease of use is quite good. The default configuration works well and all the configuration files are in XML. Documentation is available, as are online forums and IRC support. Because JBoss is so widely used, it is easy to find other experienced developers to talk to if a problem is encountered. In fact, it’s hard to fault any of the open source JMS providers in this area. JBossMQ is a great choice if you are running the JBoss Application Server. Unfortunately, it is currently being rewritten to rely on the JBoss CMP for persistence. This means that there is a dependency on the JBoss application server. The JMX interfaces are excellent and performance is good. As a quick ramp-up developer environment, it is a great choice.