bug #7342
closedincomplete bean initialization with specific data causes LIEs
0%
Description
this has been observed at the salvador portal where a lot of functionality is broken due to LazyInitializationException
which happen lately:
potentially a duplicate of #7331 yet unconfirmed
- does not return data for search
- opening the taxa returns "Taxon does not exist"
- expand ANGIOSPERMAE in the taxontree does not work, expand GYMNOSPERMAE works, but the children can not be expanded
affected web service calls with the resulting LazyInitializationException
¶
Caused by: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: eu.etaxonomy.cdm.model.agent.Team.teamMembers, could not initialize proxy - no Session at org.hibernate.collection.internal.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:567) at org.hibernate.collection.internal.AbstractPersistentCollection.withTemporarySessionIfNeeded(AbstractPersistentCollection.java:205) at org.hibernate.collection.internal.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:546) at org.hibernate.collection.internal.AbstractPersistentCollection.read(AbstractPersistentCollection.java:133) at org.hibernate.collection.internal.PersistentList.iterator(PersistentList.java:132) at eu.etaxonomy.cdm.strategy.cache.agent.TeamDefaultCacheStrategy.getNomenclaturalTitle(TeamDefaultCacheStrategy.java:83) at eu.etaxonomy.cdm.strategy.cache.agent.TeamDefaultCacheStrategy.getNomenclaturalTitle(TeamDefaultCacheStrategy.java:1) at eu.etaxonomy.cdm.model.agent.Team.getNomenclaturalTitle(Team.java:261) at sun.reflect.GeneratedMethodAccessor7586.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:79) at eu.etaxonomy.cdm.model.agent.TeamOrPersonBase_$$_jvst73e_61.getNomenclaturalTitle(TeamOrPersonBase_$$_jvst73e_61.java) at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getAuthorAndExAuthor(TaxonNameDefaultCacheStrategy.java:260) at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getNonCacheAuthorshipCache(TaxonNameDefaultCacheStrategy.java:202) at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getAuthorshipCache(TaxonNameDefaultCacheStrategy.java:176) at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getTaggedTitle(TaxonNameDefaultCacheStrategy.java:413) at eu.etaxonomy.cdm.model.name.TaxonName.getTaggedName(TaxonName.java:1427) at eu.etaxonomy.cdm.remote.json.processor.bean.TaxonNameBeanProcessor.processBeanSecondStep(TaxonNameBeanProcessor.java:66) at eu.etaxonomy.cdm.remote.json.processor.bean.TaxonNameBeanProcessor.processBeanSecondStep(TaxonNameBeanProcessor.java:25) at eu.etaxonomy.cdm.remote.json.processor.bean.AbstractBeanProcessor.processBean(AbstractBeanProcessor.java:167) at net.sf.json.JSONObject._fromBean(JSONObject.java:676)
Caused by: org.hibernate.LazyInitializationException: could not initialize proxy - no Session at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:148) at org.hibernate.Hibernate.initialize(Hibernate.java:62) at eu.etaxonomy.cdm.hibernate.HibernateProxyHelper.deproxy(HibernateProxyHelper.java:58) at eu.etaxonomy.cdm.model.common.CdmBase.deproxy(CdmBase.java:306) at eu.etaxonomy.cdm.strategy.cache.taxon.TaxonBaseDefaultCacheStrategy.getNameTags(TaxonBaseDefaultCacheStrategy.java:95) at eu.etaxonomy.cdm.strategy.cache.taxon.TaxonBaseDefaultCacheStrategy.getTaggedTitle(TaxonBaseDefaultCacheStrategy.java:65) at eu.etaxonomy.cdm.model.taxon.TaxonBase.getTaggedTitle(TaxonBase.java:221) at eu.etaxonomy.cdm.remote.json.processor.bean.TaxonBaseBeanProcessor.processBeanSecondStep(TaxonBaseBeanProcessor.java:54) at eu.etaxonomy.cdm.remote.json.processor.bean.TaxonBaseBeanProcessor.processBeanSecondStep(TaxonBaseBeanProcessor.java:25) at eu.etaxonomy.cdm.remote.json.processor.bean.AbstractBeanProcessor.processBean(AbstractBeanProcessor.java:167) at net.sf.json.JSONObject._fromBean(JSONObject.java:676)
Files
Related issues
Updated by Katja Luther over 5 years ago
for example portal/classification/b010c84d-6049-45f4-9f13-c065101eaa26/childNodesOf/a7d542c5-1ae2-4edd-9f46-445b9b7f6f0c fails with lazyLoadingException - no Session (all clicks for opening a taxon result in LazyInitiolisationExceptions)
clicking on ANGIOSPERMAE results in:
"This concept of the taxon ANGIOSPERMAE sec. Berendsohn & al. 2009-2016 is not contained as an accepted taxon in the currently chosen classification, but in this one: Nova Silva Cuscatlanica" but "Nova Silva Cuscatlanica" is the default classification and there is only one classification.
Updated by Katja Luther over 5 years ago
- Related to bug #7331: AdvancedBeanInitializer fails to initialize properties of preinitialized beans in the graph in very special situations added
Updated by Andreas Kohlbecker over 5 years ago
- Tags set to salvador
- Subject changed from Salvador portal does not return data to incomplete bean initialization with specific data
- Description updated (diff)
- Category set to cdmlib-remote
Updated by Andreas Kohlbecker over 5 years ago
- Subject changed from incomplete bean initialization with specific data to incomplete bean initialization with specific data causes LIEs
ich habe den cdm-server heute morgen um 2018-04-05 08:51:14 neu gestartet, weil der swap-space wieder mal sehr stark beansprucht war. Vorher hatte ich noch dieses Ticket um Stacktraces ergänzt. Seit dem ist das Problem anscheinen verschwunden.
Tritt das Problem möglicherweise dann auf, wenn der Server zu stark belastet ist?
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 5.0 to Release 5.1
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 5.1 to Release 5.2
Updated by Andreas Müller about 5 years ago
- Target version changed from Release 5.2 to Release 5.3
Updated by Katja Luther about 5 years ago
- Target version changed from Release 5.3 to Release 5.4
Updated by Andreas Müller almost 5 years ago
- Target version changed from Release 5.4 to Release 5.5
Updated by Andreas Müller over 4 years ago
- Target version changed from Release 5.5 to Release 5.6
Updated by Andreas Müller over 4 years ago
- Target version changed from Release 5.6 to Reviewed Next Major Release
Updated by Andreas Müller almost 2 years ago
- Status changed from New to Resolved
- Assignee changed from Katja Luther to Andreas Kohlbecker
- Target version changed from Reviewed Next Major Release to Release 5.43
As I can't reproduce any of the LIEs anymore I suggest to close this ticket as worksforme (and remove target version). Instead reopen new ticket if the problem occurs again.
Updated by Andreas Kohlbecker almost 2 years ago
- Status changed from Resolved to Worksforme
- Target version deleted (
Release 5.43)