THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The connection url defines the values that are common across the cluster of brokers. The virtual host is second in the list as the AMQP specification demands that it start with a '/' otherwise it be more readable to be swapped with clientid. There is currently only one required option and that is the '''brokerlist''' option. In addition the following options are recognised.
...
There are currently quite a few default values that can be assumed. This was done so that the current client examples would not have to be re-written. The result is if there is no transport, 'tcp' is assumed and the default AMQP port of 5672 is used if no port is specified.
'''Transport''' |
|---|
tcp |
vm |
Currently only 'tcp' and 'vm' transports are supported. Each broker can take have additional options that are specific to that broker. The following are currently implemented options. To add support for further transports the ''client.transportTransportConnection'' class needs updating along with the parsing to handle the transport.
'''Option''' ''' | Default''' ' | ''Description''' |
|---|---|---|
retries | 1 | The number of times to retry connection to this Broker |
ssl | false | Use ssl on the connection |
connecttimeout | 30000 | How long in (milliseconds) to wait for the connection to succeed |
Brokerlist failover option
...
Currently implemented failover methods.
'''Method''' ''' | Description''' |
|---|---|
singlebroker | This will only use the first broker in the list. |
roundrobin | This method tries each broker in turn. |
The current defaults are naturally to use the 'singlebroker' when only one broker is present and the 'roundrobin' method with multiple brokers. The '''method''' value in the URL may also be any valid class on the classpath that implements the FailoverMethod interface.
...