true a separate thread is used for dispatching messages for each Session in the Connection.
A separate thread is always used when there's more than one session, or the session isn't in
MessageProducer will always use Sync sends when sending a Message even if it is not required for the Delivery Mode.
The size of the message window that will be audited for duplicates and out of order messages.
Maximum number of producers that will be audited.
true the consumer will check for duplicate messages and properly handle the message to make sure that it is not processed twice inadvertently.
Sets the JMS clientID to use for the connection.
Sets the timeout, in milliseconds, before a close is considered complete. Normally a
close() on a connection waits for confirmation from the broker.
This allows the close operation to timeout preventing the client from hanging when no broker is available.
Controls whether message expiration checking is done in each
MessageConsumer prior to dispatching a message. Disabling this check can lead to consumption of expired messages. (since 5.11).
Should a JMS message be copied to a new JMS Message object as part of the
send() method in JMS. This is enabled by default to be compliant with the JMS specification.
For a performance boost set to
false if you do not mutate JMS messages after they are sent.
Sets whether or not timestamps on messages should be disabled or not.
For a small performance boost set to
Should the broker dispatch messages asynchronously to the consumer?
Controls whether Structured Message Properties and MapMessages are supported so that Message properties and
MapMessage entries can contain nested Map and List objects. Available from version 4.1.
When an object is set on an
ObjectMessage the JMS spec requires the object be serialized by that set method.
true the object will not be serialized. The object may subsequently be serialized if the message needs to be sent over a socket or stored to disk.
Enables an optimized acknowledgement mode where messages are acknowledged in batches rather than individually. Alternatively, you could use
Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the consumers which can often be faster.
WARNING: enabling this issue could cause some issues with auto-acknowledgement on reconnection.
If > 0, specifies the max time, in milliseconds, between batch acknowledgements when
optimizeAcknowledge is enabled. (since 5.6).
If > 0, specifies a time interval upon which all the outstanding ACKs are delivered when optimized acknowledge is used so that a long running consumer that doesn't receive any more messages will eventually ACK the last few un-ACK'ed messages (since 5.7).
true a larger prefetch limit is used - only applicable for durable topic subscribers.
Forces the use of Async Sends which adds a massive performance boost; but means that the
send() method will return immediately whether the message has been sent or not which could lead to message loss.
Enables the use of compression on the message's body.
Sets whether or not retroactive consumers are enabled. Retroactive consumers allow non-durable topic subscribers to receive old messages that were published before the non-durable subscriber started.
The timeout, in milliseconds, from the time of connection creation to when a warning is generated if the connection is not properly started via Connection.start() and a message is received by a consumer. It is a very common gotcha to forget to start the connection and then wonder why no messages are delivered so this option makes the default case to create a warning if the user forgets.
To disable the warning just set the value to