You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2015/09/22 17:15:04 UTC
[jira] [Issue Comment Deleted] (ARTEMIS-225) Incomplete Activation
Validation
[ https://issues.apache.org/jira/browse/ARTEMIS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic updated ARTEMIS-225:
------------------------------------
Comment: was deleted
(was: The "fix" I sent to validate the activation spec breaks the TCK so I'm going to revert that and focus on resolving the NPE itself. [~jmesnil], can you provide a stack-trace for the NPE you're seeing?)
> 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)