-->
edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help >

Configure queues


A JMS queue is based on the point-to-point (PTP) messaging model, which enables one application to send a message to another. PTP messaging applications send and receive messages using named queues. A queue sender (producer) sends a message to a specific queue. A queue receiver (consumer) receives messages from a specific queue.

You configure queues explicitly or by configuring a JMS template that can be used to define multiple queues with similar option settings, as described in Configure JMS templates.

Note: To help manage recovered or rolled back messages, you can also configure a target error destination for messages that have reached their redelivery limit. However, the error destination must be targeted to same JMS server as the other queues in a module. See Programming WebLogic JMS.

Some queue options are dynamically configurable. When options are modified at runtime, only incoming messages are affected; stored messages are not affected.

To configure a queue in JMS system module:

  1. If necessary, configure a JMS system module for the queue. See Configure JMS system modules.

  2. Before creating a queue resource in a module, optionally create other quota, template, and destination key resources in the module that can be referenced from within the queue:

  3. Create queues in a system module

    After creating a basic queue, you can define a number of optional properties:

    1. Configure general queue parameters

      Configuring optional General queue properties includes selecting a destination key for sorting messages as they arrive on the queue, or selecting a JMS template if you are using one to configure properties for multiple queues.

    2. Configure advanced queue parameters

      Configuring optional Advanced queue properties includes specifying unit-of-order parameters, attaching the credentials of message senders, or defining unit-of-work parameters.

    3. Configure queue thresholds and quota

      Define upper and lower byte and/or message thresholds for the queue, select a pre-configured quota specifying the maximum number of bytes or messages that the queue is allowed to store, or specify a maximum size allowed for messages on the queue.

    4. Configure message delivery overrides

      Define message delivery override values, such as message priority and time-to-deliver values, that can override those specified by a message producer.

    5. Configure queue message logging

      Enable the logging of message life cycle information into a JMS message log file. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

    6. Configure queue message delivery failure options

      Define default message delivery failure values, such as defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired messages.

  4. If you skipped the targeting step when you created a queue, or want to change the queue's selected subdeployment, you can do so at anytime. See Specify a subdeployment for queues.

  5. Optionally, add or remove security roles and policies to a queue. See Create queue security roles and Configure queue security policies.

  6. In the event that you need to troubleshoot a queue, you can temporarily pause all message production, insertion (in-flight messages), and consumption operations on the queue. Queues can be paused either on a WebLogic Server restart or at runtime.

Related Tasks

Related Topics

} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i