EAP7: Artemis RA vs AMQ 7 - provide more detailed description of the configuration

Latest response

Hello,
the EAP 7(.1) document Configuring Messaging, chapter 31.3. Configuring the Artemis Resource Adapter to Connect to Red Hat JBoss AMQ 7 doesn't cover much detail for more advanced scenarios. For example:

  1. For most of additional connection properties, it's theoretically possible to specify them at 2 places:
  • on the pooled connection factory, e.g.
/subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra-remote:write-attribute(name=retry-interval,value=1000)
  • as additional parameters in the URL (java.naming.provider.url) in the external-context bindings, e.g.
java.naming.provider.url = tcp://localhost:61616?retryInterval=1000

I suppose the connection factory should be the primary target of such advanced configuration. However how about the java.naming.provider.url in the external-context bindings? If that URL should be configured in such way as well It would be good to somehow cover that. At least in the form of a brief mention with the link pointing to the appropriate place.

  1. (dummy entry to correct the numbering)

  2. Similarly, if I want to specify multiple brokers to connect to (cluster), how it should be done? Again I expect that using multiple connectors by the connection factory is the thing to do, however should these multiple brokers be actually configured at both places (pooled-connection-factory & java.naming.provider.url)? Or AMQ user+password?

  3. Minor glitch/inconsistency: in "3. Add a pooled connection factory for the remote connector." the CLI example created a connection factory named activemq-ra-remote, however the XML example that follows shows its name being remote-artemis.

  4. In the same paragraph "3. Add a pooled connection factory for the remote connector." the space delimited specification of multiple JNDI names: entries=[java:/RemoteJmsXA java:jboss/RemoteJmsXA] leads to a little weird behavior at EAP 7.1 - the connection factory is bound under the name "java:/RemoteJmsXA java:jboss/RemoteJmsXA" instead of those 2 names separately. If comma is used as a delimiter then this doesn't happen.

Note: There are many those connection properties, starting with clientID, ha, retryInterval and many others that can be found for example here:

The pooled connection factory advanced settings are somewhat documented (above linked A.3. Pooled Connection Factory Attributes ), however if the URL (java.naming.provider.url) should be configured in a similar manner as well, then these advanced properties should be documented somwhere. At least in a brief form with links to the Artemis documentation or so.

PH

Responses