Table 13-4
Attribute Label
|
Description
|
Value Constraints
|
Name
|
The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: Name
|
|
JNDIName
|
The JNDI name used to look up the connection factory within the JNDI namespace. The connection factory name is configured separately.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: JNDIName
|
|
Client Id
|
The client ID for a durable subscriber that uses this connection factory.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: ClientId
|
Dynamic: yes
|
Default Priority
|
The default priority used for messages when a priority is not explicitly defined.
Message producers can get the priority explicitly by calling the javax.jms.MessageProducer.getPriority() method.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: DefaultPriority
|
Minimum: 0
Maximum: 9
Default: 4
Dynamic: yes
|
Default Time To Live
|
The maximum length of time, in milliseconds, that a message will exist. This value is used for messages when a priority is not explicitly defined. A value of 0 indicates that the message has an infinite amount time to live.
Message producers can get the time-to-live explicitly by calling the javax.jms.MessageProducer.getTimeToLive() method.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: DefaultTimeToLive
|
Minimum: 0
Maximum: 9223372036854775807
Default: 0
Dynamic: yes
|
Default Time To Deliver
|
The delay time, in milliseconds, between when a message is produced and when it is made visible on its destination.
Message producers can get the time-to-deliver explicitly by calling the weblogic.jms.extensions.WLMessageProducer.getTimeToDeliver() method.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: DefaultTimeToDeliver
|
Minimum: 0
Maximum: 9223372036854775807
Default: 0
Dynamic: yes
|
Default Delivery Mode
|
The default delivery mode used for messages when a delivery mode is not explicitly defined.
Message producers can get the delivery mode explicitly by calling the javax.jms.MessageProducer.getDeliveryMode() method.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: DefaultDeliveryMode
|
Default: Persistent
Valid values:
Dynamic: yes
|
Default Redelivery Delay
|
The delay time, in milliseconds, before rolled back or recovered messages are redelivered.
Message consumers can get the redelivery delay explicitly by calling the weblogic.jms.extensions.WLSession.getRedliveryDelay() method.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: DefaultRedeliveryDelay
|
Minimum: 0
Maximum: 9223372036854775807
Default: 0
Dynamic: yes
|
Messages Maximum
|
The maximum number of messages that can exist for an asynchronous session and that have not yet been passed to the message listener. A value of -1 indicates that there is no limit on the number of messages. In this case, however, the limit is set to the amount of remaining virtual memory.
When the number of messages reaches the MessagesMaximum value:
For multicast sessions, when a connection is stopped, messages will continue to be delivered, but only until the MessagesMaximum value is reached. Once this value is reached, messages will be discarded based on the Overrun policy.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: MessagesMaximum
|
Minimum: -1
Maximum: 2147483647
Default: 10
Dynamic: yes
|
Overrun Policy
|
The policy to use when the number of outstanding multicast messages reaches the value specified in MessagesMaximum and some messages must be discarded.
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.
Message age is defined by the order of receipt, not by the JMSTimestamp value.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: OverrunPolicy
|
Default: KeepOld
Valid values:
Dynamic: yes
|
Allow Close In On Message
|
Specifies whether the connection factory creates message consumers that allow a close() method to be issued within its onMessage() method call.
If selected (true), a close() method call from within an onMessage() method call will succeed instead of blocking forever. If the acknowledge mode of the session is set to AUTO_ACKNOWLEDGE, the current message will still be acknowledged automatically when the onMessage() call completes.
This attribute is dynamic and can be changed at any time. However, changing the value does not affect existing connections. It only affects new connections made with this connection factory.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: AllowCloseInOnMessage
|
Default: false
Valid values:
Dynamic: yes
|
Acknowledge Policy
|
Note: This attribute only applies to implementations that use the CLIENT_ACKNOWLEDGE acknowledge mode for a non-transacted session.
This attribute works around a change in the JMS specification. Specifically, the specification allowed users to acknowledge all messages before and including the message geing acknowledged. The specification was changed so that acknowledging any message acknowledges all messages ever received (even those received after the message being acknowledge), as follows:
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: AcknowledgePolicy
|
Default: All
Valid values:
Dynamic: yes
|
Load Balancing Enabled
|
Specifies whether non-anonymous producers created through a connection factory are load balanced on a per-call basis.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: LoadBalancingEnabled
|
Default: true
Valid values:
Dynamic: yes
|
Server Affinity Enabled
|
Specifies whether a WebLogic Server that is load balancing consumers or producers across multiple physical destinations in a distributed destination set, will first attempt to load balance across any other physical destinations that are also running on the same WebLogic Server.
MBean: weblogic.management. configuration. JMSConnectionFactoryMBean
Attribute: ServerAffinityEnabled
|
Default: true
Valid values:
Dynamic: yes
|