[jboss-jira] [JBoss JIRA] (AS7-830) using JMSQueueService to create and bind queues to new contexts with previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on context heritage

[Jeff Mesnil (JIRA)]

    [ https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682066#comment-12682066 ] 

Jeff Mesnil commented on AS7-830:
---------------------------------

I can't reproduce it with the CLI:

{noformat}
[standalone at localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-queue=test/:add(entries=["queue/foo/bar/baz/tacos/someQueue"])
{"outcome" => "success"}
[standalone at localhost:9999 /] /subsystem=messaging/hornetq-server=default/jms-queue=test2/:add(entries=["queue/foo/bar/baz/gouda/anotherQueue"])
{"outcome" => "success"}
[standalone at localhost:9999 /] /subsystem=messaging/hornetq-server=default/:read-resource(recursive=true)
{
    "outcome" => "success",
    ...
        "jms-queue" => {
            "test2" => {
                "durable" => true,
                "entries" => ["queue/foo/bar/baz/gouda/anotherQueue"],
                "selector" => undefined
            },
            "test" => {
                "durable" => true,
                "entries" => ["queue/foo/bar/baz/tacos/someQueue"],
                "selector" => undefined
            }
        },
    ...
}
{noformat}

bob, is it still an issue?
                
> using JMSQueueService to create and bind queues to new contexts with previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on context heritage
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-830
>                 URL: https://issues.jboss.org/browse/AS7-830
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 7.0.0.Beta3
>            Reporter: Bob McWhirter
>            Assignee: Jeff Mesnil
>
> If I hijack JMSQueueService, and attempt to bind the queue as queue/foo/bar/baz/tacos/someQueue, it may work the first time, but subsequent created queues end up with a duplicated section in the resulting path.  Trying to bind to queue/foo/bar/baz/gouda/anotherQueue might result in queue/foo/bar/baz/tacos/gouda/anotherQueue.
> Seems some stack doesn't get completely popped when HornetQ goes creating parent contexts in order to plant the leaf resource.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira