Regression in 2.0.2 for autoconfiguration order?

[iNikem]

After upgrading from 2.0.0 to 2.0.2 we face an issue similar to #4781 . After some investigation it seems that in version 2.0.2 Hibernate gets initialised before EhCacheCacheConfiguration thus leading to double cache initialisation and failure. I can confirm that in 2.0.1 the order is the correct one

[iNikem]

It seems that although EhCacheCacheConfiguration is still processed before HibernateJpaAutoConfiguration the first time when CacheManager bean is requested is long after Hibernate was initialised.

May be important aspect is that CacheManager bean is requested by our own library which exposes beans as autoconfiguration itself...

[snicoll]

@iNikem There was an early initialization bug in the cache infrastructure that got fixed so I think that whatever problem you're experiencing is there since the beginning and hidden behind that bug. To go further, please share a sample we can run ourselves that reproduces the problem.

[iNikem]

I am unable to create a standalone reproducible example for this problem. It seems that our complex setup screws things in some non-obvious way. I have a workaround for this, so it is not a blocker for us.

[wilkinsona]

Thanks for following up, @iNikem. If you manage to create a reproducible example please let us know and we can re-open this issue.

[snicoll]

@iNikem I believe @vpavic managed to create a sample which is working properly now, see #14181. If you're still affected by this, perhaps you can try 2.0.5.BUILD-SNAPSHOT to see if that helps.