Component
|
JMS Attribute
|
Description
|
JMS Connection Factories
|
Message Maximum
|
Maximum number of messages that can exist for an asynchronous session and that have not yet been passed to the message listener. This attribute defaults to 10.
|
Overrun Policy
|
Overrun policy for multicast sessions. When the number of outstanding messages reaches the Messages Maximum attribute value, messages are discarded based on the specified policy.
If set to KeepNew, the most recent messages are given priority over the oldest messages, and the oldest messages are discarded, as needed. If set to KeepOld, the oldest messages are given priority over the most recent messages, and the most recent messages are discarded, as needed.
This attribute defaults to KeepOld.
|
Allow Close In OnMessage
|
Flag for specifying whether a connection factory creates message consumers that allow a close() method to be issued within its onMessage() method call. This attribute is disabled by default.
|
Transaction Timeout
|
Timeout value (in milliseconds) for transacted sessions. This attribute defaults to 3600.
|
User Transactions Enabled
|
Flag for specifying whether a connection factory creates sessions that are JTA aware. This attribute is disabled by default.
|
|
Default Redelivery Delay
|
Default time delay, in milliseconds, before rolled back or recovered messages are redelivered. This attribute defaults to 0.
|
|
Default Time To Deliver
|
Default time delay, in milliseconds, between when a message is produced and when it is made visible on its destination. This attribute defaults to 0.
|
|
XA Connection Factory Enabled
|
Flag for specifying whether or not an XA queue or XA topic connection factory is returned, instead of a queue or topic connection factory. It can be used to return a XA queue session or XA topic session, which has the getXAResource method.
|
|
Acknowledge Policy
|
The message acknowledge policy for the connection factory. This attribute only applies to implementations that use the CLIENT_ACKNOWLEDGE acknowledgement mode for a non-transacted session. Valid values are:
- All—acknowledge all messages ever received by a given session, regardless of which message calls the acknowledge method.
- Previous—acknowledge all messages received by a given session, but only up to and including the message that calls the acknowledge method.
This attribute defaults to All.
|
JMS Servers
|
JMS Default Connection Factories Enabled
|
Flag specifying whether the JMS default connection factories are instantiated on the JMS server. This attribute is enabled by default.
|
|
Bytes Paging Enabled
|
- If the Bytes Paging Enabled check box is not selected (False), then server bytes paging is explicitly disabled.
- If the Bytes Paging Enabled check box is selected (True), a paging store has been configured, and both the Bytes Threshold Low and Bytes Threshold High attributes are greater than -1, then server bytes paging is enabled.
- If either the Bytes Threshold Low or Bytes Threshold High attribute is undefined, or defined as -1, then server bytes paging is implicitly disabled—even though the Bytes Paging Enabled check box is selected (True).
|
|
Messages Paging Enabled
|
- If the Messages Paging Enabled check box is not selected (False), then server messages paging is explicitly disabled.
- If the Messages Paging Enabled check box is not selected (False), then server messages paging is explicitly disabled.
- If either the Messages Threshold Low or Messages Threshold High attribute is undefined, or defined as -1, then server paging is implicitly disabled—even though the Messages Paging Enabled check box is selected (True).
|
|
Paging Store
|
The name of the persistent store where non-persistent messages are paged. A paging store cannot be the same store used for persistent messages or durable subscribers.
Two JMS servers cannot use the same paging store; therefore, you must configure a unique paging store for each server.
|
JMS Destinations
|
Enable Store
|
Flag specifying whether the destination uses the backing store specified by the JMS server.
If this flag is enabled, but no backing store is defined, then the configuration fails and WebLogic JMS does not boot. If this flag is disabled, then the destination does not support persistent messages. If this flag is set to Default, then the destination uses the backing store if one is defined.
This attribute defaults to Default.
|
Multicast Address
|
IP address used for multicasting. This address is used to transmit messages to multicast consumers. This attribute has no default.
|
Multicast TTL
|
Time-to-live value used for multicasting, specifying the number of routers that the message can traverse en route to the consumers. This attribute defaults to 0.
|
Multicast Port
|
IP port used for multicasting. This port is used to transmit messages to multicast consumers. This attribute defaults to 6001.
|
|
Time To Deliver Override
|
Defines the default delay, in milliseconds, between when a message is produced and when it is made visible on its destination, regardless of the delivery time specified by the producer and/or connection factory. The default value (-1) specifies that the destination will not override the Time To Deliver setting.
|
|
Delivery Mode Override
|
Delivery mode assigned to all messages that arrive at the destination regardless of the delivery mode specified by the message producer. The default value of No-Delivery specifies that the delivery mode will not be overridden.
|
|
Redelivery Limit
|
The number of redelivery tries a message can have before it is placed in the error destination. Depending on whether an error destination is configured, the following occurs when the redelivery limit is reached:
- If no error destination is configured, or the quota for the error destination would be exceeded, then persistent and non-persistent messages are simply dropped.
- If an error destination is configured and the error destination is at quota, then an error message is logged and the message is dropped. However, if the message is persistent, it remains in the persistent store. This ensures that a persistent message will be redelivered when WebLogic Server is rebooted.
The default value (-1) specifies that the destination will not override the Redelivery Limit setting.
|
|
Error Destination
|
A destination for messages that have reached their redelivery limit. If the error destination is null, then such messages are simply dropped. This attribute is dynamically configurable, but only incoming messages are impacted; stored messages are not impacted. This attribute defaults to none.
|
|
Bytes Paging Enabled
|
- If Bytes Paging Enabled is set to False, then destination-level bytes paging is disabled for this destination.
- If Bytes Paging Enabled is set to True, a paging store has been configured for the JMS Server, and both the Bytes Threshold Low and Bytes Threshold High attributes are greater than -1, then destination-level bytes paging is enabled for this destination.
- If Bytes Paging Enabled is set to Default, then this value inherits the template's value—if a template is specified. If no template is configured for the destination, then the Default value is equivalent to False.
|
|
Messages Paging Enabled
|
- If Messages Paging Enabled is set to False, then destination-level messages paging is disabled for this destination.
- If Messages Paging Enabled is set to True, a paging store has been configured for the JMS Server, and both the Messages Threshold Low and Messages Threshold High attributes are greater than -1, then destination-level messages paging is enabled for this destination.
- If Messages Paging Enabled is set to Default, then this value inherits the template's value—if a template is specified. If no template is configured for the destination, then the Default value is equivalent to False.
|
JMS Template
|
Bytes Paging Enabled
|
- If the Bytes Paging Enabled check box is not selected (False), then destination-level bytes paging is disabled for the JMS template's destinations—unless the destination setting overrides the template.
- If the Bytes Paging Enabled check box is selected (True), a paging store has been configured for the JMS Server, and both the Bytes Threshold Low and Bytes Threshold High attributes are greater than -1, then destination-level bytes paging is enabled for the JMS template's destinations—unless the destination setting overrides the template.
- If no value is defined in the JMS Template MBean, then the value defaults to False and bytes paging is disabled for the JMS template's destinations.
|
|
Messages Paging Enabled
|
- If the Messages Paging Enabled check box is not selected (False), then destination-level messages paging is disabled for the template's destination—unless the destination setting overrides the template.
- If the Messages Paging Enabled check box is selected (True), a paging store has been configured for the JMS Server, and both the Messages Threshold Low and Messages Threshold High attributes are greater than -1, then destination-level messages paging is enabled for this destination—unless the destination setting overrides the template.
- If no value is defined in the JMS Template MBean, then the value defaults to False and messages paging is disabled for the template's destinations.
|