[
https://issues.apache.org/jira/browse/ARTEMIS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903230#comment-14903230
]
ASF GitHub Bot commented on ARTEMIS-225:
----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/173
Revert "ARTEMIS-225 validate clientID is set for durable sub"
This reverts commit 1c933cfbaeae6518e2fcf55bcb58f3b714f04370.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis master-revert
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/173.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #173
----
commit 7a337a7e552c0679d80ef2600c2ef6f7daf954ba
Author: Clebert Suconic <[email protected]>
Date: 2015-09-22T00:39:07Z
Revert "ARTEMIS-225 validate clientID is set for durable sub"
This reverts commit 1c933cfbaeae6518e2fcf55bcb58f3b714f04370.
----
> Incomplete Activation Validation
> --------------------------------
>
> Key: ARTEMIS-225
> URL: https://issues.apache.org/jira/browse/ARTEMIS-225
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Jeff Mesnil
> Assignee: Justin Bertram
> Fix For: 1.2.0, 1.1.1
>
>
> When a MDB is deployed with the activation config property
> subscriptionDurability set to Durable but without a required clientId
> property, it generates NPE in our app server since the RA tries to create a
> queue which name is an non-null empty string.
> When the Activation validate its spec, it should verify the presence of the
> clientId property if the subscriptionDurability is Durable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
