en.help.task-jmsphysicaldestnew.html Maven / Gradle / Ivy

Go to download



To Create a 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.


In the navigation tree, expand the Configuration node.
Under the Configuration node, expand the Java Message Service node.
Under the Java Message Service node, select the Physical Destinations node.The Physical Destinations page opens.
On the Physical Destinations page, click New.The New Physical Destination page opens.
In the Name field, type the name of the physical destination.
From the Type drop-down list, select either javax.jms.Topic or javax.jms.Queue.
In the Maximum Number of Unconsumed Messages field, type 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.
In the Maximum Message Size field, type the maximum size, in bytes, of
any single message.A value of –1 denotes an unlimited message size. The default value is
–1.
In the Maximum Total Memory field, type 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.
From the Threshold Limit Behavior drop-down list, select the behavior the broker is
to follow when the memory-limit threshold is reached.
Reject newest messages tells the broker to reject the newest messages and to notify the
producing client with an exception only if the message is persistent.Reject newest messages is the default value.
Slow down producers tells the broker to slow the rate at which message producers send
messages.
Throw out oldest tells the broker to discard the oldest messages.
Throw out lowest-priority messages tells the broker to 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.
In the Maximum Number of Producers field, type 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.
In the Batch Delivery Max Message Count field, type 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.
From the Use Dead Message Queue drop-down list, select True to place dead
messages in the dead message queue.If the value is set to False, dead messages are discarded. This option
is set to True by default.
From the Validate XML Schema Enabled drop-down list, select True to enable XML
schema validation for the destination.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.
In the XML Schema URI List field, type 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.
See Also
To Configure the JMS Service


To Create a JMS Host


To Edit a JMS Host


To Delete a JMS Host


To Edit a JMS Physical Destination


To Delete a JMS Physical Destination


To Remove Messages from a JMS Physical Destination


To View Statistics for a JMS Physical Destination




Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices