The table in this topic describes the JMS runtime properties set
when creating a service with a message binding.
These runtime properties are set when defining endpoints used for a
message service sending outbound messages. You can also edit these runtime
properties in the Properties view of the Service editor.
Table 1. JMS
| Property
|
Description
|
| Non XA Queue Session Acknowledge Mode
|
Select one of the following:
-
AUTO_ACKNOWLEDGE - The session automatically acknowledges a client's receipt of
a message when it has either successfully returned from a call to receive or
the MessageListener it has called to process the message successfully returns.
-
CLIENT_ACKNOWLEDGE - The client acknowledges a message by calling the message's
acknowledge method. Acknowledging a consumed message automatically acknowledges
the receipt of all messages that have been delivered by its session.
-
DUPS_OK_ACKNOWLEDGE - This option instructs the session to lazily acknowledge
the delivery of messages. If JMS fails, duplicate messages may be delivered.
Use of this option can reduce session overhead because the session minimizes
the work that prevents duplicates.
|
| Non XA Queue Transacted
|
Select True or False
|
| Timeout
|
Specify the timeout for a transaction. The default
value is 3000 seconds.
|
| XA Support
|
Select one of the following to specify if you want to
support transactionality:
|
Send your feedback on this help topic to Sybase Technical Publications:
pubs@sybase.com
Your comments will be sent to the technical publications staff at Sybase, Inc.
For product-related issues or technical support, contact Sybase Technical Support
at 1-800-8SYBASE.