-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Hi everyone,
Facing the following issue in spring 2.1.3.RELEASE.
[java.lang.IllegalStateException: Expected lazy evaluation to yield a non-null value but got null! at org.springframework.data.util.Lazy.get(Lazy.java:97) at org.springframework.data.mapping.model.AbstractPersistentProperty.hashCode(AbstractPersistentProperty.java:323) at java.util.HashMap.hash(HashMap.java:339) at java.util.HashMap.get(HashMap.java:557) at org.springframework.data.mapping.PreferredConstructor.isConstructorParameter(PreferredConstructor.java:135) at org.springframework.data.mapping.model.BasicPersistentEntity.isConstructorArgument(BasicPersistentEntity.java:137) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.readProperties(MappingMongoConverter.java:364) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.populateProperties(MappingMongoConverter.java:295) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.read(MappingMongoConverter.java:275) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.read(MappingMongoConverter.java:245) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.read(MappingMongoConverter.java:194) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.read(MappingMongoConverter.java:190) at org.springframework.data.mongodb.core.convert.MappingMongoConverter.read(MappingMongoConverter.java:78) at org.springframework.data.mongodb.core.MongoTemplate$ReadDocumentCallback.doWith(MongoTemplate.java:3017) at org.springframework.data.mongodb.core.MongoTemplate.executeFindOneInternal(MongoTemplate.java:2626) at org.springframework.data.mongodb.core.MongoTemplate.doFindOne(MongoTemplate.java:2353) at org.springframework.data.mongodb.core.MongoTemplate.findOne(MongoTemplate.java:769) at org.springframework.data.mongodb.core.MongoTemplate.findOne(MongoTemplate.java:757) at
Background:
We are using multiple mongo templates in our services and each service is auto-scaled based on demand.
Unable to reproduce this error in non-production environment. Can anyone help me with this?