You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Ben O'Day (JIRA)" <ji...@apache.org> on 2014/06/06 06:33:02 UTC
[jira] [Comment Edited] (AMQ-5211)
ActiveMQDestination.createDestination() should prevent empty destination
name
[ https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019562#comment-14019562 ]
Ben O'Day edited comment on AMQ-5211 at 6/6/14 4:32 AM:
--------------------------------------------------------
patch to add validation with simple unit tests for empty queue/topic names and fixed a few typos
was (Author: boday):
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)