edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Configure connection

Configure connection factory flow control

After you configure a connection factory, you can define a number of flow control parameters. Flow control allows you to tell a JMS server or destination to slow down message producers when it determines that it is becoming overloaded. Specifically, when a JMS server or destination exceeds its specified bytes or messages thresholds, it instructs producers to limit their message flow (messages per second).

To configure message flow control on a connection factory:

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

2. In the Administration Console, navigate to the connection factory resource that you want to configure:

   • Navigate to JMS Resources in System Modules

   • Navigate to JMS resources in an application module

3. Click the Configuration > Flow Control tab.

4. If you are using the Flow Control feature:

   1. In Flow Control Enabled, specify whether a producer can be flow controlled by the JMS server. If enabled, the associated message producers will be slowed down if the JMS server reaches its upper bytes and/or messages threshold settings.

   2. In Flow Maximum, specify the maximum number of messages per second for a producer that is experiencing a threshold condition. When a producer is flow controlled it will never be allowed to go faster than the Flow Maximum messages per second setting.

   3. In Flow Minimum, specify the minimum number of messages per second for a producer that is experiencing a threshold condition. This is the lower boundary of a producer's flow limit. That is, WebLogic JMS will not further slow down a producer whose message flow limit is at its Flow Minimum.

   4. In Flow Interval, specify an adjustment period of time, defined in seconds, when a producer adjusts its flow from the Flow Maximum number of messages to the Flow Minimum amount, or vice versa.

   5. In Flow Steps, specify the number of steps used when a producer is adjusting its flow from the Flow Minimum amount of messages to the Flow Maximum amount, or vice versa.

   6. In Send Timeout, specify the maximum number of milliseconds that a producer will wait for sufficient space (quota) on a JMS server or destination to accommodate the message being sent.

   For more information about these fields, see Configuration Options.

5. If you are using the One-Way Send feature to allow producers to send one-way messages without internally waiting for a response from the target destination's host JMS server.

   1. In One-Way Send Mode, specify whether message producers created using this connection factory are allowed to do one-way message sends to improve typical non-persistent, non-transactional messaging performance. You can choose to allow queue senders and topic publishers to do one-way sends, or to limit this capability to topic publishers only.

   2. In One-Way Send Window Size, specify the maximum number of sent messages per window when the One-Way Send Mode field is set to either Queue or Topic or Topic Only to allow queue senders and/or topic publishers to make one-way sends. The specified window size determines when a two-way message is required to regulate the producer before it can continue making additional one-way sends. To benefit from one-way performance, the default value of 1 must be configured higher in addition to enabling the one-way send mode.

      Note: One-way message sends are disabled if your connection factory is configured with XA Connection Factory Enabled. This setting disables one-way sends whether or not the sender actually uses transactions.

   For more information about these fields, see Configuration Options.

6. Save your changes:

   • Save Changes to JMS Resources in System Modules

   • Save changes to JMS resources in an application module

7. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
   Not all changes take effect immediately—some require a restart (see Use the Change Center).

} } (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