[ https://issues.jboss.org/browse/WFLY-3493?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-3493: ---------------------------------------- [~jmesnil] This is due to how OperationContextImpl.ServiceRemovalVerificationHandler works. The OC tracks what services are removed via the OC removeService API, and in the JMSQueueRemove case that is just the JMSQueueService. The ServiceRemovalVerificationHandler then reports a failure and triggers rollback if one of those services shows up in the containerStateChangeReport.getMissingServices() map. But the service that is missing is not the service that is removed, it is a JNDI binding one: 15:16:04,467 INFO [org.jboss.as.controller] (management-handler-thread - 5) JBAS014774: Service status report JBAS014775: New missing/unsatisfied dependencies: service jboss.naming.context.java.queue.demo (missing) dependents: [service jboss.naming.context.java.module.luckywinner.luckywinner.env."org.jboss.as.demos.luckywinner.webapp.LuckyWinnerServlet".queue] So the JNDI binding is being removed, but the significance of that is unknown to the management layer. -- This message was sent by Atlassian JIRA (v6.2.6#6264)