ActiveMQ - QuickLinks

ActiveMQ implements a REST-ful API to messaging which allows any web capable device to publish or consume messages using a regular HTTP POST or GET.

If you are working with DHTML or web browsers you might wanna check out our Ajax support.

Mapping of REST to JMS

To publish a message use a HTTP POST. To consume a message use HTTP DELETE or GET.

ActiveMQ has a Servlet that takes care of the integration between HTTP and the ActiveMQ dispatcher.

You can map a URI to the servlet and then use the relative part of the URI as the topic or queue name. e.g. you could HTTP POST to

http://www.acme.com/queue/orders/input

which would publish the contents of the HTTP POST to the orders.input queue on JMS.

Similarly you could perform a HTTP DELETE GET on the above URL to read from the same queue. In this case we will map the MessageServlet from ActiveMQ to the URI

http://www.acme.com/queue

and configure it to accept the URI as a queue destination. We can do similar things to support topic destinations too.

We can use the HTTP session to denote a unique publisher or consumer.

Note that strict REST requires that GET be a read only operation; so strictly speaking we should not use GET to allow folks to consume messages. Though we allow this as it simplifies HTTP/DHTML/Ajax integration somewhat.

For a more cleaner mapping of a simple transfer protocol to different languages, you might wanna take a look at Stomp.

Timeouts

When reading from a queue we might not have any messages. We can use a timeout query parameter to indicate how long we are prepared to wait for a message to arrive. This allows us to poll or block until a message arrives.

Couple this with HTTP 1.1 keep-alive sockets and pipeline processing we can have efficient access to JMS over HTTP.

Obviously if your client is Java then using ActiveMQ's JMS API is the fastest and most efficient way to work with the message broker; however, if you are not using Java or prefer the simplicity of HTTP then it should be fairly efficient, especially if your HTTP client supports keep-alive sockets and pipeline processing.

Creating the ActiveMQ Release

Grab the latest source from SVN

svn co svn+ssh://svn.activemq.org/scm/activemq/trunk/activemq
+cd activemq

Change the version number: (we so need to make this step automatic) : + + + + + + + + + + + +

project.xml

etc/project.xml

the WireFormat version (if needed.)

Let Maven build, test, package, and deploy the binaries

maven clean default multiproject:deploy dist:deploy

Tag the release using your local workspace to a new ACTIVEMQ_X_Y label

svn mkdir svn+ssh://svn.activemq.org/scm/activemq/tags/ACTIVEMQ_X_Y -m "ActiveMQ X.Y Release"
+svn copy ../activemq svn+ssh://svn.activemq.org/scm/activemq/tags/ACTIVEMQ_X_Y/activemq -m "ActiveMQ X.Y Release"

Check that the binaries look fine.

Announcing the ActiveMQ Release

Perform a release in JIRA and create a new release version in JIRA

Create a download page for the release in the WIKI similar like the ActiveMQ 3.0 Release

Update the Xml Reference page with a link to the HTML and XSD

Mail the dev & user lists

Post a news entry on the WIKI

Have a beer!

Introduction

ActiveMQ includes a Java Connector Architecture (JCA) 1.5 Resource Adapter. JCA 1.5 defines the contract between an J2EE application server and external resources such as databases and messaging middleware. It allows the application server to efficiently pool connections, control transactions and manage security. The Resource Adapter allows ActiveMQ to be used from any J2EE 1.4 application server such as Geronimo 1.x, JBoss 4.x, and WebSphere 6.x.

Features

Inbound connection delivers messages to MDBs via XA or local transactions.

Outbound connections support standard container pooling or can reuse the inbound connection/session to avoid XA.

JTA support: Can be enlisted in XA and local transactions.

XA transaction recovery via XAResource.recover() supported.

When used outside a JTA transaction, session transaction settings retain normal JMS semantics so that it be used by your web-app tier.

Can configure and start up embedded broker.

Can connect to external ActiveMQ broker or embedded broker.

Inbound message delivery supports fine grain control of concurrency and prefetching.

Batching so that multiple messages can be delivered within the same transaction for optimal performances.

Overview

Community

Using ActiveMQ

Features

Connectivitiy

Utilities

External Tools

Related Projects

Support

Developers

Tools we use

Feeds

Overview

Community

Using ActiveMQ

Features

Connectivitiy

Utilities

External Tools

Related Projects

Support

Developers

Tools we use

Feeds

Mapping of REST to JMS

Timeouts

Overview

Community

Using ActiveMQ

Features

Connectivitiy

Utilities

External Tools

Related Projects

Support

Developers

Tools we use

Feeds

Creating the ActiveMQ Release

Announcing the ActiveMQ Release

Overview

Community

Using ActiveMQ

Features

Connectivitiy

Utilities

External Tools

Related Projects

Support

Developers

Tools we use

Feeds

Use RAID disks

Clustered JDBC databases

Use C-JDBC

SAN or shared network drive

A clustered ActiveMQ MessageStore

Overview

Community

Using ActiveMQ

Features

Connectivitiy

Utilities

External Tools

Related Projects

Support

Developers

Tools we use

Feeds

Introduction

Features

Downloading the RAR

Deployment Guides

Configuration Reference