[hibernate-dev] NotYetReadyException with extended bean manager

[Benjamin Confino]

Hello

I have a stack, see the attached file, where there is a 
NotYetReadyException. This is after liberty invokes 
ExtendedBeanManagerSynchronizer.beanManagerInitialized, and we are passing 
in a bean manager to hibernate. 

My question is what happens between 
ExtendedBeanManagerSynchronizer.beanManagerInitialized and 
ContainerManagedLifecycleStrategy$BeanImpl.resolveContainerInstance to 
result in this error? Is it still using the same BeanManager we passed in 
- and if so what could cause a NotYetReadyException when a bean manager is 
there? Or does hibernate try to acquire a second bean manager? If so what 
method does hibernate use to acquire the bean manager?

Regards
Benjamin



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Stack.txt
Url: http://lists.jboss.org/pipermail/hibernate-dev/attachments/20190701/ca4d0be1/attachment.txt