Enhance Artemis jms auto configuration

[pax95]

Currently you can only auto configure a single broker using the host and port options.
It seems not possible to set other cluster or ha attributes on the auto create ActiveMQConnectionFactory that is created without ha enabled.

It would be nice if you could use auto configuration to configure those options as well. Maybe expose a new property = url that could be used to construct the ActiveMQConnectionFactory

In that way you could set the url property in the configuration to e.g. spring.artemis.url=(tcp://localhost:61616,tcp://localhost:61716)?ha=true&retryInterval=1000&retryIntervalMultiplier=1.0&reconnectAttempts=-1

[wilkinsona]

Looking at the Artemis code, it doesn't appear to be possible to construct a connection factory with a URL without losing some control over the transport configuration. Currently, we explicitly configure the use of NettyConnectorFactory. As far as I can tell, we'd lose that if we moved to using the URL-based constructor.

Unless there's a way that can please everyone, I'm leaning towards this not be supported by auto-configuration. @pax95 There's a very good chance that you know more about configuring Artermis than I do, perhaps you can guide us towards a way that will work?

[pax95]

It seems that the transport configuration actually makes use of NettyConnectorFactory when constructing the connection factory from a URL.

Small sample with a Camel route:

    @ConfigurationProperties(prefix = "spring.artemis")
    public class AmqConfig {
        private String url;

        @Bean("connectionFactory")
        public ConnectionFactory connectionFactory() {
            ActiveMQConnectionFactory cf = new ActiveMQConnectionFactory(this.url);
            LOG.info("cf info {}", cf);
            return cf;
        }

        public void setUrl(String url) {
            this.url = url;
        }

    }

    @Component
    class MyRoute extends RouteBuilder {

        @Override
        public void configure() throws Exception {
            from("jms:foo?connectionFactory=#connectionFactory").transacted().log("log recieved");

            from("timer:bar").setBody(constant("the message")).transacted().log("sending").to("jms:foo?connectionFactory=#connectionFactory");
        }

    }

The log statement when setting the property
spring.artemis.url=(tcp://localhost:61616,tcp://localhost:61716)?ha=true&retryInterval=1000&retryIntervalMultiplier=1.0&reconnectAttempts=-1

ActivemqTestApplication     : cf info ActiveMQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=null, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61616&host=localhost&retryIntervalMultiplier=1-0&reconnectAttempts=-1&ha=true&retryInterval=1000, TransportConfiguration(name=null:tcp://localhost:61716, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?port=61716&host=localhost&retryIntervalMultiplier=1-0&reconnectAttempts=-1&ha=true&retryInterval=1000], discoveryGroupConfiguration=null], clientID=null, consumerWindowSize = 1048576, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false]

I will push the sample to GitHub later.

[pax95]

@wilkinsona Pushed a small example here https://github.com/pax95/activemq-test
The example uses just a single broker to make et easy to setup, but the url constructor seems flexible to allow cluster, ha and other properties to be embedded.

[wilkinsona]

A url property is going to get a bit messy when coupled with the existing host and port properties. We have that elsewhere though and have managed to deal with it.

[pax95]

agreed. Thats why I wanted to hear your opinion. Btw the Activemq auto configuration actually has a brokerUrl property too.

[chanjarster]

@pax95 Agree with you.

@wilkinsona I think the url version is more flexible then the host:port version. considering the following artemis url:

tcp://localhost:61616?type=CF\
  &useGlobalPools=false\
  &threadPoolMaxSize=10\
  &retryInterval=2000\
  &retryIntervalMultiplier=1.5\
  &maxRetryInterval=30000\
  &reconnectAttempts=-1

The url version gives you more control.

BTW, I implemented a customized ArtemisConfiguration by using ConnectionFactoryParser:

import org.apache.activemq.artemis.uri.ConnectionFactoryParser;

...

public ConnectionFactory connectionFactory() throws Exception {
  ConnectionFactoryParser parser = new ConnectionFactoryParser();
  return parser.newObject(parser.expandURI(artemisProperties.getUri()), "someCFConfig");
}