[jboss-jira] [JBoss JIRA] (WFLY-3493) Messaging subsystem allows you to remove a destination even though it has an attached client

[Jeff Mesnil (JIRA)]

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

Jeff Mesnil commented on WFLY-3493:
-----------------------------------

> Hmm, there's also an MDB in a separate deployment that uses the queue, and I'm not seeing anything about that dependency being broken.

The dependency between the MDB and the Queue is not the same than when using an @Resource annotation. It goes through the indirection of the activation config property and it looks like the JNDI dependency is not set up at all in that case. I'll open a separate issue for this use case.

> Messaging subsystem allows you to remove a destination even though it has an attached client
> --------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3493
>                 URL: https://issues.jboss.org/browse/WFLY-3493
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS
>    Affects Versions: 8.1.0.Final
>         Environment: WildFly 8.1 Final
>            Reporter: Tom Ross
>            Assignee: Jeff Mesnil
>
> Currently jboss-cli allows a queue to be removed even though there is a MDB attached to it. The command 
> {noformat}
> /subsystem=messaging/hornetq-server=default/jms-queue=testQueue:remove()
> {noformat}
> will remove the queue without a warning. This is not desirable since a warning should be given or a reload should be force.  It may also break the dependency injection. 



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)