You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/09/17 22:47:04 UTC

[jira] [Commented] (ARTEMIS-225) Incomplete Activation Validation

    [ https://issues.apache.org/jira/browse/ARTEMIS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804472#comment-14804472 ] 

ASF GitHub Bot commented on ARTEMIS-225:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/171

    ARTEMIS-225 validate clientID is set for durable sub

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-225

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/171.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 #171
    
----
commit 1c933cfbaeae6518e2fcf55bcb58f3b714f04370
Author: jbertram <jb...@apache.org>
Date:   2015-09-17T20:46:18Z

    ARTEMIS-225 validate clientID is set for durable sub

----


> 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
>            Reporter: Jeff Mesnil
>            Assignee: Justin Bertram
>
> 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)