Questions about the "Messaging configuration" documentation

[wolfgangknauf]

Hi all,

two questions about the Messaging configuration document at https://docs.jboss.org/author/display/WFLY8/Messaging+configuration

First: is my observation correct that WildFly 8 autocreates a queue if there is no config in standalone-full.xml and no "...-jms.xml" file in the ejb jar?

I observed this behavior with this ejb config:

@MessageDriven (activationConfig=

  {

    @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),

    @ActivationConfigProperty(propertyName="destination", propertyValue="jms/queue/MessageBeanQueue")

  })

public class MessageBean implements MessageListener

{

Is this an expected behavior? Or is it controlled by some switch?

Second: the doc contains some CLI snippets for adding a queue. It seems those are no longer correct. Instead of "jms-queue add --name=myQueue --entries=queues/myQueue" I had to use "jms-queue add --queue-address=myQueue --entries=queue/myQueue"

Similar problem for the sample "read-resource" call, which follows the "jms-queue add" snippet.

For me, it worked only with this syntax: "/subsystem=messaging/hornetq-server=default/jms-queue=myQueue:read-resource"  (added "hornetq-server=default")

Could the doc be updated please?

Thanks

Wolfgang

[wolfgangknauf]

Hi,

just want to bring this back.

Could someone take a look at the doc maybe-errors?

And it would be great if someone could bring some clarification on my question about autocreation.

Thanks

Wolfgang

[jmesnil]

Wolfgang Knauf wrote:

Hi all,

two questions about the Messaging configuration document at https://docs.jboss.org/author/display/WFLY8/Messaging+configuration

First: is my observation correct that WildFly 8 autocreates a queue if there is no config in standalone-full.xml and no "...-jms.xml" file in the ejb jar?

No, queues are not auto-created in WildFly. You *must* define them prior to use them.

Note that if you are using JMS 2.0 you can use annotations (http://docs.oracle.com/javaee/7/tutorial/doc/jms-concepts005.htm#BABHFBDH) in your applications instead of defining them in standalone-full.xml or -jms.xml file.

Could the doc be updated please?

I've fixed it. Thanks for the feedback

[wolfgangknauf]

Thanks!

It turned out that the phantom auto-creation of Queues was some confusion on my side (probably to much playing around with/without standalone-full.xml and "...jms.xml" config)...

Many thanks for pointing me to the new JMS 2.0 config capabilities. Next thing to do for me: make it run in my sample ;-)

Best regards

Wolfgang