jndi

Indicates that JNDI should be used to lookup the connection factory for creating JMS connections.

When using jndi the address portion of the binding descriptor is used as the address at which to lookup the connection factory. The returned connection factory may connect to a different host. 

jndi_contextfactory

jndi_principal

jndi_credentials

jndi_connectionfactory

The username to supply in the credentials when opening the JMS connection

Specifies whether a client_id should be set for the connection.

When true Connection.setClientID(String) is set on the JMS connection. It is important that the client id be set when using Guaranteed Qos subscriptions as the durable subscriptions issued by the binding are tied to the ClientID.

When set to true, the client id X-SMA-<busname>-<bususer> will be used as the JMS ClientID unless "use_legacy_client_id" or "client_id" are set.

Note that the bususer value used in the ClientID is the username supplied during bus creation to identify the logical bus user not the username used in the credentials for connecting to the JMS broker.

If the JMS connection is created from a JNDI connection factory that provides a pre configured JMS ClientID it may cause the JMS provider to throw an exception when the client id is set. Consequently, this value should be set to false if the connection factory is supplying the client id.

Prior to the 3.8 release the ActiveMQ specific provider set a client of <username><busname>. The change to "X-SMA<busname>-<bususername>" is a breaking change in this case for applications that have existing durable subscriptions associated with the old Client ID. The property use_legacy_client_id=true can be set to use the old client id.

Specifies that the legacy client id should be used.

When set to true indicates that the default client of <bususer>-<busname> should be used rather than the default X-SMA-<busname>-<bususer>.

This property is ignored if "set_client_id" is false or "client_id" is used to set an explicit JMS ClientID. This property should only be set for applications that were using the activemq bus provider in 3.7 or earlier.

Can be used to specify a specific client id for the bus.

This property can be used to override the default client id when set_client_id is set to true. 

Note that if the bus is shared between multiple applications, the client id should be different for each application, but the same for primary and backup instances.

connection_open_retry_count

Property controlling number of retries to attempt after a failure to open a connection.

When a connection attempt fails with a reason that isn't known to be a permanent condition, this property controls the number of reconnect attempt to try. Reconnect attempts will be attempted at the interval specified by "connection_open_retry_interval".

connection_open_retry_interval

Property specifying the retry interval for connect open retries in seconds.

When no time unit suffix is provided for this value it is interpreted as the number of seconds between retries. Otherwise, a time suffix can be provided to qualify the unit as specified in UtlUnit.parseDuration(String, TimeUnit, TimeUnit).

The minimum allowable value for retries in 250ms, specifying a lower value will cause it to be rounded up.