This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Using ActiveMQ with EJB3 (JBoss Example)

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

I've seen numerous postings regarding ActiveMQ with EJB3, and variations of a datasource XML file for use with JBoss integration.

However, they don't quite work. Here is what worked for me, it is actually quite simple:

1. Don't use any datasource file - only the RA file is required. Put it in the `deploy' directory. The file is called activemq-rar-4.1.1.rar and it is in the ActiveMQ distribution (lib/optional/)

2. In JBoss, the @ResourceAdapter annotation must be placed on the Message Driven Bean (MDB). This may vary for other application servers.

3. Examples I've seen elsewhere show an activationConfig with destination=<a JNDI name for the queue>. This doesn't work. Put the ActiveMQ destination name in the activationConfig. There is no need to put the queue in the JNDI.

Here is a working example - for EJB3 on JBoss, no XML descriptors are needed, just the RA file and the MDB.

import org.jboss.annotation.ejb.ResourceAdapter;
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination", propertyValue="FOO.TEST"),
@ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="Auto-acknowledge")
public class TestBean implements MessageListener {

public TestBean() {

public void onMessage(Message message) {