JBoss Messaging explained

JBoss Messaging
Developer:JBoss
Latest Release Version:1.4.5[1]
Discontinued:yes
Operating System:Cross-platform
Programming Language:Java
Genre:asynchronous messaging system
License:LGPL
Website:https://jbossmessaging.jboss.org/

JBoss Messaging is the JBoss enterprise asynchronous messaging system. It supersedes JBoss MQ as the default Java Message Service (JMS) provider in JBoss Application Server (JBoss AS) 5.[2] JBoss Messaging has been superseded by HornetQ, which, in turn, has been superseded by Apache ActiveMQ Artemis.[3]

JBoss Messaging 1.0 was released on 29 March 2006[4] as a re-engineered version of JBoss MQ intended to deliver a modular messaging engine capable of shipping with or without JBoss.

JBoss Messaging is the default JMS provider in JBoss Enterprise Application Platform 4.3, JBoss SOA Platform and JBoss Application Server 5.[2]

JBoss Messaging is an open source project available under the Gnu LGPL licence[1] and is led by Tim Fox with core engineers Andy Taylor, Clebert Suconic, Howard Gao and Jeff Mesnil.

On 24 August 2009, HornetQ was launched, based on the JBoss Messaging 2.0 code-base, and the JBoss Messaging project was put into bug fix mode only by JBoss.[5]

See also

External links

Notes and References

  1. Web site: JBoss Messaging - Downloads. jbossmessaging.jboss.org.
  2. Web site: JBoss Enterprise Application Platform Common Criteria Certification 5 - JBoss Messaging User Guide. docs.redhat.com.
  3. Web site: Apache ActiveMQ Artemis Hacking Guide - History. activemq.apache.org.
  4. Web site: JBoss delivers message to IBM and BEA . Gavin Clark. March 29, 2006. Reg Developer. https://web.archive.org/web/20060718140221/http://www.regdeveloper.co.uk/2006/03/29/jboss_messaging_web_server/. 2006-07-18.
  5. Web site: JBoss Messaging. jboss.org.