You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Asutosh Pandya (JIRA)" <ji...@apache.org> on 2018/03/03 19:20:00 UTC

[jira] [Updated] (AMQ-6905) Resource Adapter clientId ActivationConfigProperty does conform to API document

     [ https://issues.apache.org/jira/browse/AMQ-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asutosh Pandya updated AMQ-6905:
--------------------------------
    Attachment: AMQ-6905.patch

> Resource Adapter clientId ActivationConfigProperty does conform to API document 
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-6905
>                 URL: https://issues.apache.org/jira/browse/AMQ-6905
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: RAR
>    Affects Versions: 5.15.3
>            Reporter: Darren Merritt
>            Priority: Minor
>         Attachments: AMQ-6905.patch
>
>
> According to the following page [http://activemq.apache.org/activation-spec-properties.html]
> The clientId default is set by the resource adapter. This is not the case in the code.
> When defining the MDB to be Durable via subscriptionDurability, if the clientId is not configured an validation error is thrown stating "clientId must be set since durable subscription was requested".
> Looking at the code, if the documentation is correct, the ActiveMQActivationSpec validation method should no longer validate the clientId. The ActiveMQConnection makeConnection should change
> String clientId = activationSpec.getClientId();
> to
> String clientId = defaultValue(activationSpec.getClientId(), getInfo().getClientid());
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)