[jboss-jira] [JBoss JIRA] (WFLY-5299) WFLYWELD0001 and WFLYWELD0002 errors deploying helloworld-mbean quickstart

[Sande Gilda (JIRA)]

Sande Gilda created WFLY-5299:
---------------------------------

             Summary: WFLYWELD0001 and WFLYWELD0002 errors deploying helloworld-mbean quickstart
                 Key: WFLY-5299
                 URL: https://issues.jboss.org/browse/WFLY-5299
             Project: WildFly
          Issue Type: Bug
          Components: Web (Undertow)
            Reporter: Sande Gilda
            Assignee: Stuart Douglas


When deploying helloworld-mbean QS, WFLYWELD0001 and WFLYWELD0002 error messages are logged in server log:

{code}
ERROR [org.jboss.as.weld] (ServerService Thread Pool -- 58) WFLYWELD0001: Failed to setup Weld contexts: javax.naming.NameNotFoundException: BeanManager -- service jboss.naming.context.java.module."jboss-helloworld-mbean-helloworld-mbean-service.sar"."jboss-helloworld-mbean-helloworld-mbean-service.sar".BeanManager
ERROR [org.jboss.as.weld] (ServerService Thread Pool -- 58) WFLYWELD0002: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: BeanManager -- service jboss.naming.context.java.module."jboss-helloworld-mbean-helloworld-mbean-service.sar"."jboss-helloworld-mbean-helloworld-mbean-service.sar".BeanManager
{code}

[~jharting] said: 

        The problem is triggered by this change: https://github.com/wildfly/wildfly/commit/20bbfce9f972c73ed1c3ba250ad3f15aa0f32d96

        I am not sure why WeldContextSetup is being called for each AbstractService.invokeLifecycleMethod(). Looks like either WeldContextSetup should not be added to this particular list of setup actions or a wrong list of setup actions is used by AbstractService.

See this issue for details: https://issues.jboss.org/browse/JBEAP-625





--
This message was sent by Atlassian JIRA
(v6.4.11#64026)