
en.help.ref-jmsphysicaldestnew.html Maven / Gradle / Ivy
Show all versions of console-jms-plugin-help
New JMS Physical Destination
Use the New JMS Physical Destination page to create a new JMS
physical destination.
You do not ordinarily need to create physical destinations, because you specify a
physical destination name when you create a JMS destination resource, and the GlassFish
Server creates the physical destination automatically when it is needed.
The New JMS Physical Destination page contains the following options.
- Name
The name of the physical destination.
- Type
The type of the physical destination. Available choices are javax.jms.Topic and javax.jms.Queue.
- Maximum Number of Unconsumed Messages
The maximum number of unconsumed messages permitted for the destination. A value of –1 indicates that there is no limit to the number of unconsumed messages. The default value is –1.
- Maximum Message Size
The maximum size, in bytes, of any single message. A value of –1 denotes an unlimited message size. The default value is –1.
- Maximum Total Memory
The maximum total memory, in bytes, for unconsumed messages. A value of –1 indicates that there is no limit to the memory size for unconsumed messages. The default value is –1.
- Threshold Limit Behavior
The behavior the broker is to follow when the memory-limit threshold is reached. Available choices are:
- Reject newest messages
Reject the newest messages and notify the producing client with an exception only if the message is persistent. This is the default value.
- Slow down producers
Slow the rate at which message producers send messages.
- Throw out oldest
Discard the oldest messages.
- Throw out lowest-priority messages
Discard the messages with the lowest priority.
If the value is Throw out oldest or Throw out lowest-priority messages and Use Dead Message Queue is set to True, excess messages are moved to the dead message queue.
- Maximum Number of Producers
The maximum number of message producers that can be associated with this physical destination. When this limit is reached, no new producers can be created. A value of –1 denotes an unlimited number of producers. The default value is 100.
- Batch Delivery Max Message Count
The maximum number of messages that can be delivered to consumers in a single batch. A value of –1 denotes an unlimited number of messages. The default value is 1000.
- Use Dead Message Queue
If the value is set to True, dead messages are placed in the dead message queue. If the value is set to False, dead messages are discarded. This option is set to True by default.
- Validate XML Schema
If the value is set to True, the Message Queue client runtime will attempt to validate an XML message against the specified XML Schema Definitions (or against the DTD, if no XSD is specified) before sending it to the broker. If the specified schema cannot be located or the message cannot be validated, the message is not sent, and an exception is thrown. This option is set to False by default.
- XML Schema URI List
A space-separated list of XML Schema Definition (XSD) URI strings. If XML schema validation is enabled, the URIs point to the location of one or more XSDs to use for XML schema validation.
Related Tasks
-
-
-
-
-
-
Related asadmin Commands
Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices