Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Fri, 6 Jun 2014 04:27:01 +0000 (UTC)
From: "Ben O'Day (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12718493.1401918695326.80105.1402028821553@arcas>
In-Reply-To: <JIRA.12718493.1401918695326@arcas>
References: <JIRA.12718493.1401918695326@arcas>
Subject: [jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination()
 should prevent empty destination name
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ben O'Day updated AMQ-5211:
---------------------------

    Attachment: AMQ-5211.patch

patch to add validation with simple unit tests for empty queue/topic names...

> ActiveMQDestination.createDestination() should prevent empty destination name
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-5211
>                 URL: https://issues.apache.org/jira/browse/AMQ-5211
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.9.0
>            Reporter: Ben O'Day
>            Priority: Minor
>         Attachments: AMQ-5211.patch
>
>
> currently you can call ActiveMQDestination createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...


--
This message was sent by Atlassian JIRA
(v6.2#6252)