WFLYEJB0006: ActivationConfigProperty clientId will be ignored since it is not allowed by resource adapter: activemq-ra

[objectiser]

Hi

According to The Message-Driven Bean Class - The Java EE 6 Tutorial the 'clientId' property is valid for use with a durable subscriber. However wildfly 10.0.0.Final produces the warning in the subject line.

I would like to use the "clustered JMS durable subscription" capability of ActiveMQ Artemis which requires the same durable subscription name and client id to be set on the different nodes in the cluster.

Looks like clientId used to be supported ([WFLY-1288] Support JMS 2.0 new activation properties for MDB - JBoss Issue Tracker). Is this a bug, or can the clientId be specified in another way?

Thanks in advance.

Regards

Gary

[objectiser]

Fixed the problem - I changed "clientId" to "clientID" - based on seeing the configuration used with HornetQ.

However according to this doc (The Message-Driven Bean Class - The Java EE 6 Tutorial) the property name should be "clientId".

Should this be reported as a bug?

[jbertram]

There seems to be some ambiguity here.  The tutorial as well as the JMS 2.0 spec references "clientId" for the activation configuration property, but the API is getClientID() and setClientID(String clientID) indicating that the property's name is "clientID".  Furthermore, I would expect the JMS TCK to fail if the capitalization was strictly enforced, but I've not seen or heard of any such failures for HornetQ or Artemis.  For simplicity's sake the RA should support both "clientId" and "clientID".  Please open a JIRA at https://issues.apache.org/jira/browse/ARTEMIS.  Thanks!

[objectiser]

Done: https://issues.apache.org/jira/browse/ARTEMIS-399

Thanks.