[
https://issues.apache.org/jira/browse/AMQ-6905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976697#comment-16976697
]
ASF subversion and git services commented on AMQ-6905:
------------------------------------------------------
Commit 86e09813ae13e93fa16858c9c7e4661ebdf3f4d5 in activemq's branch
refs/heads/activemq-5.15.x from asutosh936
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=86e0981 ]
AMQ-6905 : Upgraded ActivationConfigProperty as per API Documentation
(cherry picked from commit a1f15f45111aacdde2ff883116d32aa8c14e4adc)
> 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
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 5.16.0, 5.15.11
>
> Attachments: AMQ-6905.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
