Then it means OWB is not started or the WebBeansFinder is not correct or your classloader is not stable
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> 2017-10-05 13:34 GMT+02:00 John D. Ament <[email protected]>: > These are different BeanManagerimpls > > On Oct 5, 2017 7:33 AM, "Romain Manni-Bucau" <[email protected]> > wrote: > > > Hi John, > > > > you get a new InjectableBeanManager each time yes which is wrapping the > > same BeanManagerImpl. > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://rmannibucau.metawerx.net/> | Old Blog > > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > > rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> > > > > 2017-10-05 13:18 GMT+02:00 John D. Ament <[email protected]>: > > > > > Hi, > > > > > > I'm troubleshooting an issue in Hammock where when using OWB 2.0.1 + > > Tomcat > > > 9 M26, the results of CDI.current().getBeanManager() give back > different > > > BeanManager instances. > > > > > > In fact, calling WebBeansContext.currentInstance() is returning a > > > different > > > instance on each invocation in separate threads. It's almost as if the > > > parent OWB instance is shutting down and a new instance is being > created. > > > Switching back to the main thread, I lose the original instance that I > > had. > > > > > > John > > > > > >
