[JBoss JIRA] Created: (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
8:52 p.m.
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
Affects Versions: 7.0.0.Beta3
Reporter: Bob McWhirter
Assignee: Jason Greene
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:40 a.m.
New subject: [JBoss JIRA] Updated: (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
[
https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.sy...
]
Jason Greene updated AS7-830:
-----------------------------
Assignee: (was: Jason Greene)
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
Affects Versions: 7.0.0.Beta3
Reporter: Bob McWhirter
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:10 p.m.
New subject: [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
[
https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry updated AS7-830:
---------------------------------
Component/s: JMS
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
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
6:33 p.m.
New subject: [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
[
https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.sy...
]
Stuart Douglas commented on AS7-830:
------------------------------------
Is this 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
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
8:06 a.m.
New subject: [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
[
https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.sy...
]
Jeff Mesnil reassigned AS7-830:
-------------------------------
Assignee: Jeff Mesnil
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
8:41 a.m.
New subject: [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
[
https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.sy...
]
Jeff Mesnil commented on AS7-830:
---------------------------------
I can't reproduce it with the CLI:
{noformat}
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=test/:add(entries=["queue/foo/bar/baz/tacos/someQueue"])
{"outcome" => "success"}
[standalone@localhost:9999 /]
/subsystem=messaging/hornetq-server=default/jms-queue=test2/:add(entries=["queue/foo/bar/baz/gouda/anotherQueue"])
{"outcome" => "success"}
[standalone@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
2:57 a.m.
New subject: [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
[
https://issues.jboss.org/browse/AS7-830?page=com.atlassian.jira.plugin.sy...
]
Jeff Mesnil resolved AS7-830.
-----------------------------
Resolution: Cannot Reproduce Bug
I'm closing it as I can no longer reproduce the bug with the description test case
@bob, do not hesitate to reopen it if you encounter it again
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
4351
days inactive
4736
days old
6 comments
5 participants
participants (5)
-
Bob McWhirter (JIRA) -
Brian Stansberry (Updated) (JIRA)
-
Jason Greene (JIRA)
-
Jeff Mesnil (JIRA)
-
Stuart Douglas (JIRA)