[jboss-jira] [JBoss JIRA] (WFLY-3557) Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException

[Osamu Nagano (JIRA)]

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

Osamu Nagano commented on WFLY-3557:
------------------------------------

Sample stack trace:
{code}
09:46:06,302 INFO  [stdout] (ServerService Thread Pool -- 53) --- TestValve2 : start 
09:46:06,303 INFO  [stdout] (ServerService Thread Pool -- 53) --- TestValve2 : getGlobalConfiguration
09:46:06,304 INFO  [stdout] (ServerService Thread Pool -- 53) --- TestValve2 : getGlobalConfiguration error
09:46:06,306 ERROR [stderr] (ServerService Thread Pool -- 53) javax.management.InstanceNotFoundException: jboss.web:name=TestValve,type=Valve
09:46:06,306 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:94)
09:46:06,307 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:171)
09:46:06,307 ERROR [stderr] (ServerService Thread Pool -- 53) 	at test.valve.TestValve2.getGlobalConfiguration(TestValve2.java:100)
09:46:06,307 ERROR [stderr] (ServerService Thread Pool -- 53) 	at test.valve.TestValve2.start(TestValve2.java:68)
09:46:06,308 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.apache.catalina.core.StandardPipeline.start(StandardPipeline.java:223)
09:46:06,309 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.apache.catalina.core.StandardContext.start(StandardContext.java:3713)
09:46:06,310 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156)
09:46:06,310 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60)
09:46:06,311 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93)
09:46:06,311 ERROR [stderr] (ServerService Thread Pool -- 53) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
09:46:06,311 ERROR [stderr] (ServerService Thread Pool -- 53) 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
09:46:06,312 ERROR [stderr] (ServerService Thread Pool -- 53) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
09:46:06,312 ERROR [stderr] (ServerService Thread Pool -- 53) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
09:46:06,312 ERROR [stderr] (ServerService Thread Pool -- 53) 	at java.lang.Thread.run(Thread.java:744)
09:46:06,313 ERROR [stderr] (ServerService Thread Pool -- 53) 	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
{code}

> Sever level MBean hasn't been initialized yet when a web app starts up, causing javax.management.InstanceNotFoundException
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3557
>                 URL: https://issues.jboss.org/browse/WFLY-3557
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (JBoss Web)
>    Affects Versions: JBoss AS7 7.2.0.Final
>            Reporter: Osamu Nagano
>            Assignee: Remy Maucherat
>         Attachments: module.xml, TestWAR.war, test_valve.jar
>
>
> With "-Dorg.apache.tomcat.util.ENABLE_MODELER=true", server level MBeans like a global valve become available.  Those should be visible from start phase of a web app, though sometimes those are missing and javax.management.InstanceNotFoundException is thrown.  This sporadically happens due to the parallel nature of WildFly start up.  It is reproducible by using a debugger (Eclipse is better than JDB, because JDB stops all threads).



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