Chapter 10. System Properties

Sets the AMQP version to be used - currently supports one of {0-8,0-9,0-91,0-10}.

The client will begin negotiation at the specified version and only negotiate downwards if the Broker does not support the specified version.

Defaults to the heartbeat value suggested by the Broker, if any.

Two consecutive missed heartbeats will result in the connection timing out.

This can also be set per connection using the Connection URL options.

For compatibility with old client configuration, the synonym amqj.heartbeat.delay is supported.

Setting this property to 'true' will disable that check and allow you to set a client ID of your choice later on.

Setting this property to 'false' will disable that check and allow you to ignore host name errors.

Controls whether the client will compress messages before they they are sent.

The payload size beyond which the client will start to compress message payloads.

Addressing syntax: ADDR (Address format) or BURL (Binding URL)

Maximum number of pre-fetched messages per Session. This can also be defaulted for sessions created on a particular connection using the Connection URL options.

If set will use the old map message encoding. By default the Map messages are encoded using the 0-10 map encoding.

This can also be set per connection using the Connection URL options.

Controls whether the Session dispatcher thread is a daemon thread or not. If this system property is set to true then the Session dispatcher threads will be created as daemon threads. This setting is introduced in version 0.16.

If true, creating a consumer will also declare the exchange on the Broker (specified within the Binding URL associated with the Destination), creating it if is does not already exist.

If true, creating a consumer will also declare the queue on the Broker (specified within the Binding URL associated with the Destination), creating it if is does not already exist.

If true, creating a consumer will also bind the queue to the to the exchange using the routing key as a binding key. The exchange name, queue name and routing key are taken from the Binding URL associated with the Destination.

Used with the maximum delivery count feature. See Section 5.6.3, “Maximum Delivery Count” for details.

If set true, for sessions using Session#CLIENT_ACKNOWLEDGE, a sync command is sent after every message Message#acknowledge(). This ensure that the client awaits the successful processing of the acknowledgement by server before continuing.

If false, the sync is not performed. This will improve performance but will mean duplicate messages are more likely to be received following a failure.

This can also be set per connection using the Connection URL options.

If true, messages sent to Queue destinations for which cannot be routed to at least one queue on the Broker, will be returned to the application. See Section 5.5.1, “Mandatory Messages” for more details.

If true, messages sent to Topic destinations for which cannot be routed to at least one queue on the Broker, will be returned to the application. See Section 5.5.1, “Mandatory Messages” for more details..

If true, the message will be returned to the application unless the Broker is able to route the message to at least one queue with a consumer attached. See Section 5.5.3, “Immediate Messages” for more details.

Used with Section 5.5.4, “Flow Control”. The amount of time (in milliseconds) to wait before timing out.

Used with Section 5.5.4, “Flow Control”. The frequency at which the log message informing that the producer is flow controlled .

If 'all' is set then messages will be sent synchronously.

This can also be set per connection using the Connection URL options.

Specifies the thread factory to use.

If using a real time JVM, you need to set the above property to org.apache.qpid.thread.RealtimeThreadFactory.

Specifies the priority (1-99) for Real time threads created by the real time thread factory.

The length of time (in milliseconds) to wait for a synchronous operation to complete.

For compatibility with older clients, the synonym amqj.default_syncwrite_timeout is supported.

Sets the TCP_NODELAY property of the underlying socket. The default was changed to true as of Qpid 0.14.

This can also be set per connection using the Connection URL broker optiontcp_nodelay. options.

For compatibility with older clients, the synonym amqj.tcp_nodelay is supported.

Sets the SO_SNDBUF property of the underlying socket. Added in Qpid 0.16.

For compatibility with older clients, the synonym amqj.sendBufferSize is supported.

Sets the SO_RCVBUF property of the underlying socket. Added in Qpid 0.16.

For compatibility with older clients, the synonym amqj.receiveBufferSize is supported.

During failover, this is the timeout for each attempt to try to re-establish the connection. If a reconnection attempt exceeds the timeout, the entire failover process is aborted.

It is only applicable for AMQP 0-8/0-9/0-9-1 clients.

Restriction on the SASL mechanisms which can be used. More than one could be specified as a space separated list.

We currently support the following mechanisms: PLAIN GSSAPI EXTERNAL SCRAM-SHA-256 SCRAM-SHA-1 XOAUTH2 CRAM-MD5 XOAUTH2 ANONYMOUS.

This can also be set per connection using the Connection URL options.

When using GSSAPI as the SASL mechanism, sasl_protocol must be set to the principal for the qpid broker, e.g. qpidd.

This can also be set per connection using the Connection URL options.

When using GSSAPI as the SASL mechanism, sasl_server must be set to the host for the SASL server, e.g. example.com.

This can also be set per connection using the Connection URL options.

If set to 'false', forces the SASL GASSPI client to obtain the kerberos credentials explicitly instead of obtaining from the "subject" that owns the current thread.

Specifies the jass configuration file.

Ex-Djava.security.auth.login.config=myjas.conf

Here is the sample myjas.conf JASS configuration file:

		com.sun.security.jgss.initiate {
		com.sun.security.auth.module.Krb5LoginModule required useTicketCache=true;
		};

		

Timeout value used by the Java SSL engine when waiting on operations.

The key manager factory algorithm name. If not set, defaults to the value returned from the Java runtime call KeyManagerFactory.getDefaultAlgorithm()

For compatibility with older clients, the synonym qpid.ssl.keyStoreCertType is supported.

The trust manager factory algorithm name. If not set, defaults to the value returned from the Java runtime call TrustManagerFactory.getDefaultAlgorithm()

For compatibility with older clients, the synonym qpid.ssl.trustStoreCertType is supported.

Specifies the key store path.

This can also be set per connection using the Connection URL options.

Specifies the key store password.

This can also be set per connection using the Connection URL options.

Specifies the trust store path.

This can also be set per connection using the Connection URL options.

Specifies the trust store password.

This can also be set per connection using the Connection URL options.