See: Description
| Class | Description |
|---|---|
| ClientProvider | |
| ServerProvider |
JMX Remote provider for AMQP 1.0 via org.apache.qpid:qpid-jms-client:0.11.1.
Various URL query parameters control the behaviour of the the
JMS Connection; which are described in the table below. Each of these
properties can also be provided in the initial set of attributes that
is passed in JMXConnectorServerFactory#newJMXConnectorServer or JMXConnectorFactory#newJMXConnector(). All keys are case sensitive
| Attribute/Parameter | Description |
|---|---|
jmx.type |
The destination type (i.e. Topic or Queue;
case-sensitive); defaults to Topic.
|
jmx.destination |
The name of a Topic or Queue; if not assigned, then a unique one will be created to avoid exceptions; this is, though, pointless from a usability perspective |
jmx.brokerUser |
The username to connect to the broker (if required); This is likely to be redundant; as you can often configure the username directly on the URL. |
jmx.brokerPassword |
The password to connect to the broker (if required);This is likely to be redundant; as you can often configure the password directly on the URL. |
You can mix and match the environment with the URL which will be
stripped of any known parameters before being passed through to JmsConnectionFactory. If either
jmx.brokerUser or jmx.brokerPassword are specified (via URL, environment or JMXConnector.CREDENTIALS), then this will
cause ConnectionFactory.createConnection(String, String) to be
used when creating the connection.
service:jmx:amqp:///amqp://localhost:5672?jms.prefetchPolicy.all=100&jmx.type=Topic&jmx.destination=jmxTopic
will result in amqp://localhost:5672?jms.prefetchPolicy.all=100
being passed into the JmsConnectionFactory