[jboss-jira] [JBoss JIRA] (WFLY-4806) Do not deploy artifacts until subsystem MBeans are registered
Brian Riehman (JIRA)
issues at jboss.org
Sat Jun 27 17:30:02 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Riehman closed WFLY-4806.
-------------------------------
Resolution: Won't Fix
Thank you for the very helpful comments, [~kabirkhan]. Closing since this seems to be working as intended.
> Do not deploy artifacts until subsystem MBeans are registered
> -------------------------------------------------------------
>
> Key: WFLY-4806
> URL: https://issues.jboss.org/browse/WFLY-4806
> Project: WildFly
> Issue Type: Feature Request
> Components: JMX, Server
> Reporter: Brian Riehman
> Assignee: Kabir Khan
> Priority: Minor
>
> When the server starts up and begins to deploy artifacts, the subsystem MBeans are not yet available. Our application has implemented a {{ServletContextListener}} and is attempting to lookup attributes from a DataSource MBean (e.g. {{jboss.as:subsystem=datasources,xa-data-source=DefaultDS}}). This MBean is not available at the time the listener is called when the server is first starting up. Some time after the deployment has run, the MBean is available and can be queried.
> If the deployment is added after the server has already successfully started, the MBean can be queried successfully. I would imagine the deploy operation is done in parallel with the MBean registration, but I cannot find where the datasource subsystem MBean registration occurs.
> It is odd that the datasource exists but the datasources subsystem MBean is not yet available for querying.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list