Adding a JMS Queue to Jboss 7

Question

I want to try and get an understanding of how JMS works. I am going through a tutorial and have created the Producer/Consumer java classes but not sure how to create the JMS queue. I downloaded jboss-as-web-7.0.2.Final which i believe has HornetQ. I have not got anywhere so far as i just cant figure out how to add a Queue.

According to this document https://docs.jboss.org/author/display/AS7/Messaging+configuration , a queue can be added by using the add-jms-queue command. I tried it but it generates an error.

[standalone@localhost:9999 /] add-jms-queue --name=sampleQueue --entries=queue/sampleQueue

The command is not available in the current context (e.g. required subsystems or connection to the controller might be unavailable).

I also cant find an option to add the queue via the admin console on the GUI.

Any ideas?

Thanks

Solution 1

If you have JBoss 7 web (Java EE6 Certified), It doesn't contain JMS implementation (HornetQ) as it has not been approved yet. JBoss 7 Everything (NOT Java EE6 Certified) contains JMS implementation.

Solution 2

For other people which have the same message while using JBoss 7.1.x:

You should add the in the file standalone/configuration/standalone.xml a new subsystem for JMS (<subsystem xmlns="urn:jboss:domain:messaging:1.1">). You can look into the standalone/configuration/standalone-full.xml for that subsystem or simple use the standalone-full.xml.

And you should use the following command:

jms-queue add --queue-address=MyQueue --entries=queue/MyQueue,java:/jms/myApp/MyQueue

EDIT:

On WildFly you need may be also to add

<server xmlns="urn:jboss:domain:3.0">
  <extensions>
      ...
      <extension module="org.jboss.as.messaging"/>
  </extensions>
</server>

Comments

[ziggy]

ah thats interesting. I did download the Java EE6 Certified version. Does this mean that HornetQ might not be the JMS provider for Jboss 7?

[viktor]

I don't have that kind of information. I think it's more about some certification process that must be done first before it can be labeled as implementation of Java EE 6 spec.