javax.naming.NamingException

WELD-001300 Unable to locate BeanManager

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web740

  • WELD-001300: Unable to locate BeanManager
  • via omnifaces.org by Unknown author, 11 months ago
    WELD-001300: Unable to locate BeanManager
  • WELD-001300 Unable to locate BeanManager
  • Stack trace

    • javax.naming.NamingException: WELD-001300 Unable to locate BeanManager at org.jboss.weld.resources.ManagerObjectFactory.getObjectInstance(ManagerObjectFactory.java:47) at org.apache.tomee.catalina.TomcatResourceFactory.create(TomcatResourceFactory.java:73) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.xbean.recipe.ObjectRecipe.internalCreate(ObjectRecipe.java:298) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:96) at org.apache.xbean.recipe.AbstractRecipe.create(AbstractRecipe.java:61) at org.apache.openejb.assembler.classic.Assembler.createResource(Assembler.java:2201) at org.apache.openejb.config.ConfigurationFactory.install(ConfigurationFactory.java:436) at org.apache.openejb.config.AutoConfig.installResource(AutoConfig.java:2074) at org.apache.openejb.config.AutoConfig.processApplicationResources(AutoConfig.java:976) at org.apache.openejb.config.AutoConfig.deploy(AutoConfig.java:185) at org.apache.openejb.config.ConfigurationFactory$Chain.deploy(ConfigurationFactory.java:401) at org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:962) at org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1214) at org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1087) at org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:130) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5378) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1083) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1880) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.