Exception after upgrade of Spring Boot from Version 2.5.7 to 2.5.8

[khmarbaise]

We are using blaze persistence 1.6.4 (also tested with 1.6.6):

11:06:49  	at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
11:06:49  	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
11:06:49  Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'AAAAService': Unsatisfied
dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean
 with name 'abcccStreamProvider': Unsatisfied dependency expressed through constructor parameter 1; nested exception is
 org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'ABCService': Unsatisfied dependency expressed
  through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name
  'AAAAService': Unsatisfied dependency expressed through constructor parameter 0; nested exception is
  org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'blazeService':
  Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error
  creating bean with name 'getCriteriaBuilderFactory' defined in XXXXConfig:
  Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate
  [com.blazebit.persistence.CriteriaBuilderFactory]: Factory method 'getCriteriaBuilderFactory' threw exception; nested exception is
  java.util.ServiceConfigurationError: com.blazebit.persistence.spi.EntityManagerFactoryIntegrator: Provider
  com.blazebit.persistence.integration.hibernate.Hibernate53EntityManagerFactoryIntegrator could not be instantiated
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:800)
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:229)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1372)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1222)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
11:06:49  	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
11:06:49  	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
11:06:49  	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
11:06:49  	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
11:06:49  	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:953)
11:06:49  	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:918)
11:06:49  	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583)
11:06:49  	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:765)
11:06:49  	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:445)
11:06:49  	at org.springframework.boot.SpringApplication.run(SpringApplication.java:338)
11:06:49  	at org.springframework.boot.test.context.SpringBootContextLoader.loadContext(SpringBootContextLoader.java:121)
11:06:49  	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContextInternal(DefaultCacheAwareContextLoaderDelegate.java:99)
11:06:49  	at org.springframework.test.context.cache.DefaultCacheAwareContextLoaderDelegate.loadContext(DefaultCacheAwareContextLoaderDelegate.java:124)
11:06:49  	... 71 more
11:06:49  Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name
'abcccStreamProvider': Unsatisfied dependency expressed through constructor parameter 1; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'ABCService':
Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException:
Error creating bean with name 'AAAAService': Unsatisfied dependency expressed through constructor parameter 0; nested exception is
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'blazeService': Unsatisfied dependency expressed through
 constructor parameter 1; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name
 'getCriteriaBuilderFactory' defined in XXXXConfig: Bean instantiation via factory method failed;
 nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.blazebit.persistence.CriteriaBuilderFactory]:
 Factory method 'getCriteriaBuilderFactory' threw exception; nested exception is java.util.ServiceConfigurationError: com.blazebit.persistence.spi.EntityManagerFactoryIntegrator:
 Provider com.blazebit.persistence.integration.hibernate.Hibernate53EntityManagerFactoryIntegrator could not be instantiated
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:800)
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:229)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1372)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1222)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:582)
11:06:49  	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542)
11:06:49  	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335)
11:06:49  	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)
11:06:49  	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333)
11:06:49  	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208)
11:06:49  	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:276)
11:06:49  	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1389)
11:06:49  	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1309)
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:887)
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:791)
11:06:49  	... 89 more

What me puzzles a bit is that in the stack trace the Hibernate53EntityManagerFactoryIntegrator which I figured out that this is defined in blaze-persistence-integration-hibernate-5.4-1.6.4.jar.

Does someone has a hint what might the cause of this problem?

[beikov]

Hi @khmarbaise, it seems like the integration couldn't be setup correctly for some reason. Is there no other stacktrace that points to the actual exception?

[beikov]

Such an error usually pops up when working in uber-jar mode and the reason for this is that the Hibernate version can't be determined. Are you running in uber jar mode?

[khmarbaise]

First thanks for your questions. Here is more of the stack trace...

11:06:49  Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.blazebit.persistence.CriteriaBuilderFactory]: Factory method
 'getCriteriaBuilderFactory' threw exception; nested exception is java.util.ServiceConfigurationError: com.blazebit.persistence.spi.EntityManagerFactoryIntegrator: 
 Provider com.blazebit.persistence.integration.hibernate.Hibernate53EntityManagerFactoryIntegrator could not be instantiated
11:06:49  	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185)
11:06:49  	at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:653)
11:06:49  	... 159 more
11:06:49  Caused by: java.util.ServiceConfigurationError: com.blazebit.persistence.spi.EntityManagerFactoryIntegrator: 
Provider com.blazebit.persistence.integration.hibernate.Hibernate53EntityManagerFactoryIntegrator could not be instantiated
11:06:49  	at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:582)
11:06:49  	at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:804)
11:06:49  	at java.base/java.util.ServiceLoader$ProviderImpl.get(ServiceLoader.java:722)
11:06:49  	at java.base/java.util.ServiceLoader$3.next(ServiceLoader.java:1395)
11:06:49  	at com.blazebit.persistence.impl.CriteriaBuilderConfigurationImpl.loadEntityManagerIntegrator(CriteriaBuilderConfigurationImpl.java:1914)
11:06:49  	at com.blazebit.persistence.impl.CriteriaBuilderConfigurationImpl.<init>(CriteriaBuilderConfigurationImpl.java:573)
11:06:49  	at com.blazebit.persistence.impl.CriteriaBuilderConfigurationProviderImpl.createConfiguration(CriteriaBuilderConfigurationProviderImpl.java:47)
11:06:49  	at com.blazebit.persistence.Criteria.getDefault(Criteria.java:65)
11:06:49  	at de.db.leidad.services.BasisdatenConfig.getCriteriaBuilderFactory(BasisdatenConfig.java:16)
11:06:49  	at de.db.leidad.services.BasisdatenConfig$$EnhancerBySpringCGLIB$$3ed263b0.CGLIB$getCriteriaBuilderFactory$0(<generated>)
11:06:49  	at de.db.leidad.services.BasisdatenConfig$$EnhancerBySpringCGLIB$$3ed263b0$$FastClassBySpringCGLIB$$326e86c4.invoke(<generated>)
11:06:49  	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244)
11:06:49  	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
11:06:49  	at de.db.leidad.services.BasisdatenConfig$$EnhancerBySpringCGLIB$$3ed263b0.getCriteriaBuilderFactory(<generated>)
11:06:49  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
11:06:49  	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
11:06:49  	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
11:06:49  	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
11:06:49  	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
11:06:49  	... 160 more
11:06:49  Caused by: java.lang.ExceptionInInitializerError
11:06:49  	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
11:06:49  	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
11:06:49  	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
11:06:49  	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
11:06:49  	at java.base/java.util.ServiceLoader$ProviderImpl.newInstance(ServiceLoader.java:780)
11:06:49  	... 177 more
11:06:49  Caused by: java.lang.IllegalArgumentException: Error while trying to resolve the Hibernate version. 
This can happen when using an uber-jar deployment. In that case, please provide a service provider implementation of com.blazebit.persistence.integration.hibernate.base.spi.HibernateVersionProvider
11:06:49  	at com.blazebit.persistence.integration.hibernate.base.function.AbstractHibernateEntityManagerFactoryIntegrator.<clinit>(AbstractHibernateEntityManagerFactoryIntegrator.java:96)
11:06:49  	... 182 more
11:06:49  Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 3 out of bounds for length 3
11:06:49  	at com.blazebit.persistence.integration.hibernate.base.function.AbstractHibernateEntityManagerFactoryIntegrator.<clinit>(AbstractHibernateEntityManagerFactoryIntegrator.java:93)
11:06:49  	... 182 more
11:06:49 

This being running as an integration tests within Maven Failsafe plugin.
The weird thing is that I only upgraded the spring boot version......

[beikov]

Can you set a breakpoint there to see what the Hibernate version is which is reported? I don't know what changed in the new Spring version, but maybe the classloader is somehow different now?

You can workaround this by providing a custom com.blazebit.persistence.integration.hibernate.base.spi.HibernateVersionProvider implementation and registering that via the Java service loader mechanism.

[khmarbaise]

Hi it took some time, so after detailed debugging we have found the problem.

We have found out that within AbstractHibernateEntityManagerFactoryIntegrator class the part in that class:

            String[] parts = VERSION_STRING.split("[\\.-]");
            MAJOR = Integer.parseInt(parts[0]);
            MINOR = Integer.parseInt(parts[1]);
            FIX = Integer.parseInt(parts[2]);
            TYPE = parts[3];

assumes that the Final of a version does always exists.

During the upgrade of Spring Boot 2.5.7 to 2.5.8 the version of Hibernate has been changed from 5.4.32.Final into 5.4.33.

So the simple question in the end is: Is it necessary to have that information about .Final within the version or not?

Furthermore I found that within central there existing two versions of Hibernate (for example hibernate-core)

There are existing two different versions 5.4.33 and also 5.4.33.Final with different dates of release. The first one on December 2021 whereas the second one with release date of 10. January 2022.

[beikov]

That was a mistake in the release process of Hibernate. Spring should use the correct version which is the one ending with .Final. You can update that in your pom.xml if you want, the version with .Final is equivalent to the other.

[khmarbaise]

Unfortunately spring boot uses the wrong version:

Spring boot dependencies: 2.5.7.pom:

    <hibernate.version>5.4.32.Final</hibernate.version>

And:
Spring boot dependencies: 2.5.8.pom:

    <hibernate.version>5.4.33</hibernate.version>

From my point of view is the question why the information .Final is needed somewher?

[beikov]

I guess we could ignore that part, but in the end, this is also a part of the version, which some integration specific code might need, in order to determine whether a feature is supported or not.

[khmarbaise]

Finally we have upgraded to Spring Boot 2.6.4 and the problem is a kind of solved. Thanks for your help.

[beikov]

Great to hear! You're welcome