|
|
|
|
|
Boolean |
true |
Allow auto-creation of queue destinations?
|
|
Boolean |
true |
Allow auto-creation of topic destinations? |
|
Integer |
120 seconds |
The delay, in seconds. before
which auto-created destinations are removed from the system when they no longer have
consumers nor contain messages, . A smaller value means that memory reclamation takes
place more often. |
imq.autocreate.destination.maxNumMsgs |
Integer |
100000 |
Maximum number of unconsumed messages A value of -1 denotes an
unlimited number of messages.
Note - When flow control is in effect (imq.autocreate.destination.limitBehavior = FLOW_CONTROL),
it is possible for the specified message limit to be exceeded because the
broker cannot react quickly enough to stop the flow of incoming messages. In
such cases, the value specified for imq.autocreate.destination.maxNumMsgs serves as merely a hint
for the broker rather than a strictly enforced limit. However, if the number
of unconsumed messages would exceed imq.system.max_count, the broker generates a ResourceAllocationException indicating
that the destination is full and rejecting new messages.
|
imq.autocreate.destination.maxBytesPerMsg |
String |
10k |
Maximum size, in bytes,
of any single message The value may be expressed in bytes, kilobytes, or
megabytes, using the following suffixes:
b: Bytes
k: Kilobytes (1024 bytes)
m: Megabytes (1024 × 1024 = 1,048,576 bytes)
|
|
|
|
An unsuffixed value is expressed in bytes; a
value of -1 denotes an unlimited message size. |
|
|
|
Examples:
1600: 1600 bytes
1600b: 1600 bytes
16k: 16 kilobytes (= 16,384 bytes)
16m: 16 megabytes (= 16,777,216 bytes)
-1: No limit
|
imq.autocreate.destination.maxTotalMsgBytes |
String |
10m |
Maximum total memory, in
bytes, for unconsumed messages The syntax is the same as for imq.autocreate.destination.maxBytesPerMsg (see
above). |
imq.autocreate.destination.limitBehavior |
String |
REJECT_NEWEST |
Broker behavior when memory-limit threshold reached:
FLOW_CONTROL: Slow down producers
REMOVE_OLDEST: Throw out oldest messages
REMOVE_LOW_PRIORITY: Throw out lowest-priority messages according to age; no notification to producing client
REJECT_NEWEST: Reject newest messages; notify producing client with an exception only if message is persistent
When FLOW_CONTROL is specified, it is
still possible for the number of messages to exceed imq.system.max_count. In this situation, the
broker generates a ResourceAllocationException indicating that the destination is full and rejecting new
messages. |
|
|
|
If the value is REMOVE_OLDEST or REMOVE_LOW_PRIORITY and the imq.autocreate.destination.useDMQ property is true,
excess messages are moved to the dead message queue. |
imq.autocreate.destination.maxNumProducers |
Integer |
100 |
Maximum number of message
producers for destination When this limit is reached, no new producers can be
created. A value of -1 denotes an unlimited number of producers. |
imq.autocreate.queue.maxNumActiveConsumers2 |
Integer |
-1 |
Maximum number
of active message consumers in load-balanced delivery from queue destination A value of -1
denotes an unlimited number of consumers. |
imq.autocreate.queue.maxNumBackupConsumers2 |
Integer |
0 |
Maximum number of backup message consumers in load-balanced
delivery from queue destination A value of -1 denotes an unlimited number of consumers.
|
imq.autocreate.queue.consumerFlowLimit2 |
Integer |
1000 |
Maximum number of messages delivered to queue consumer in a single batch In load-balanced
queue delivery, this is the initial number of queued messages routed to active
consumers before load balancing begins. A destination consumer can override this limit by
specifying a lower value on a connection. A value of 0 or
-1 denotes an unlimited number of messages. |
imq.autocreate.topic.consumerFlowLimit3 |
Integer |
1000 |
Maximum number of messages delivered to topic
consumer in a single batch A value of 0 or -1 denotes an unlimited
number of messages. Not used when the JMS resource adapter, jmsra, is used
to consume messages in a GlassFish Server cluster. |
imq.autocreate.topic.sharedConsumerFlowLimit3 |
Integer |
5 |
Maximum number of messages delivered
to topic consumer in a single batch when the JMS resource adapter, jmsra,
is used to consume messages in a GlassFish Server cluster A value of 0
or -1 denotes an unlimited number of messages. |
imq.autocreate.destination.isLocalOnly |
Boolean |
false |
Local delivery only? This property
applies only to destinations in broker clusters, and cannot be changed once the
destination has been created. If true, the destination is not replicated on other
brokers and is limited to delivering messages only to local consumers (those connected
to the broker on which the destination is created). |
imq.autocreate.queue.localDeliveryPreferred2 |
Boolean |
false |
Local delivery preferred?
This property applies only to load-balanced queue delivery in broker clusters. If true,
messages will be delivered to remote consumers only if there are no consumers
on the local broker; the destination must not be restricted to local-only delivery
(imq.autocreate.destination.isLocalOnly must be false). |
imq.autocreate.destination.useDMQ |
Boolean |
true |
Send dead messages to dead message queue? If false,
dead messages will simply be discarded. |
validateXMLSchemaEnabled |
Boolean |
false |
XML schema validation is enabled? If set
to false or not set, then XML schema validation is not enabled for
the destination. |
XMLSchemaURIList |
String |
null |
Space separated list of XML schema document (XSD) URI strings The
URIs point to the location of one or more XSDs to use
for XML schema validation, if enabled. Use double quotes around this value if
multiple URIs are specified. Example: “http://foo/flap.xsd http://test.com/test.xsd” If this property is not set or null and
XML validation is enabled, XML validation is performed using a DTD specified in
the XML document. |
reloadXMLSchemaOnFailure |
Boolean |
false |
Reload XML schema on failure enabled? If set to false or
not set, then the schema is not reloaded if validation fails. |