Several parameters concerning how the JMS server should behave with regard to their clients can be configured with the client parameters bean. For example, the "client-id" a client should have when using this connection factory can be configured with a client parameter bean.
If you use the getMBeanInfo
operation in MBeanTypeServiceMBean, supply the following value as this MBean's fully qualified interface name:
weblogic.j2ee.descriptor.wl.ClientParamsBean
No factory methods. Instances of this MBean are created automatically.
You can access this MBean from the following MBean attributes:
|
This section describes the following attributes:
Acknowledge policy for non-transacted sessions that use the
CLIENT_ACKNOWLEDGE
mode. All
indicates
that calling acknowledge on a message acknowledges all
unacknowledged messages received on the session.
Previous
specifies that calling acknowledge on a
message acknowledges only unacknowledged messages up to, and
including, the given message.
This parameter works around a change in the JMS specification
and only applies to implementations that use the
CLIENT_ACKNOWLEDGE
acknowledge mode for a
non-transacted session. Specifically, the specification allowed
users to acknowledge all messages before and including the message
being acknowledged. The specification was changed so that
acknowledging any message acknowledges all messages ever received
(even those received after the message being acknowledge).
ACKNOWLEDGE_PREVIOUS
retains the old behavior
(acknowledge all message up to and including the message being
acknowledged). Whereas, ACKNOWLEDGE_ALL
yields the new
behavior, where all messages received by the given session are
acknowledged regardless of which message is being used to effect
the acknowledge.
Privileges | Read/Write |
Type | java.lang.String |
Default Value | All |
Legal Values |
|
Specifies whether the connection factory creates message
consumers that allow a close()
method to be issued
within its onMessage()
method call.
If selected, 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.
If not selected, it will cause the stop()
and
close()
methods to hang if called from
onMessage()
.
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.
Privileges | Read/Write |
Type | boolean |
Default Value | true |
An optional client ID for a durable subscriber that uses this JMS connection factory. Configuring this value on the connection factory prevents more than one JMS client from using a connection from the factory.
Generally, JMS durable subscriber applications set their client
IDs dynamically using the
javax.jms.Connection.setClientID()
call.
Privileges | Read/Write |
Type | java.lang.String |
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, new messages are discarded according the
policy specified by the OverrunPolicy
parameter and a
DataOverrunException is thrown.
For non-multicast sessions, new messages are flow-controlled, or retained on the server until the application can accommodate the messages.
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.
Privileges | Read/Write |
Type | int |
Default Value | 10 |
The policy to use when the number of outstanding multicast messages reaches the value specified in MessagesMaximum and some messages must be discarded.
Keep New
indicates that the most recent messages are given priority over the oldest messages, and the oldest messages are discarded, as needed.
Keep Old
indicates that 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.
Privileges | Read/Write |
Type | java.lang.String |
Default Value | KeepOld |
Legal Values |
|
This section describes the following operations:
|
Return true if the given property has been explicitly set in this bean.
Operation Name | "isSet" |
Parameters | Object [] {
propertyName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
boolean
|
java.lang.IllegalArgumentException
Restore the given property to its default value.
Operation Name | "unSet" |
Parameters | Object [] {
propertyName }
where:
|
Signature | String [] {
"java.lang.String" } |
Returns |
void
|
java.lang.IllegalArgumentException