Consultor Eletrônico

SUMMARY:

This solution applies to SonicMQ Version 2000.x and 3.x.

You must create queues in the SonicMQ database administratively via
the Explorer, the Admin shell, or, beginning with SonicMQ 3.x, via the
BrokerManager prior to using them in a QueueSender or QueueReceiver.

EXPLANATION:

SonicMQ 2000.1 allows you to create topics dynamically from a JMS
messaging client, but queues do not have this "dynamic" capability
because the ability to create Queues/Topics dynamically was not
something specified in the JMS specification Version 1.0.1.

Queues are administered objects, and therefore you can create a Queue
object even though you cannot use it in a QueueSender or
QueueReceiver. This behavior is specified in the JMS spec version
1.0.1.

The Queue objects can be created independently of any JMS connection
or session (and generally stored in a JNDI store). It is only an error
to "bind" the Queue to a QueueConnection that can't support it.

With SonicMQ 3.x, Queues can now be created programatically using the
BrokerManager API:

BrokerManager.setQueue(java.lang.String queue, boolean global,
boolean readExclusive, int retrieveThreshold,
int saveThreshold, int maxQueueSize)


References to Written Documentation:

SonicMQ 2000.x Installation and Administration Guide,
Chapter 3, "Graphical Administration Tool"
Chapter 4, "Command-line Administration Tool"


SonicMQ 3.x Installation Administration & Configuration Guide,
Chapter 3, "Graphical Administration Tool"
Chapter 4, "Command-line Administration Tool"


SonicMQ 3.x Programming Guide,
Chapter 10, "Management API"

SonicMQ 3.x Online BrokerManager API Reference