Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Description
When deploying helloworld-mbean QS, WFLYWELD0001 and WFLYWELD0002 error messages are logged in server log:
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
rhn-engineering-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
Attachments
Issue Links
- blocks
-
JBEAP-625 Errors when deploying helloworld-mbean QS
- Closed