bug #8866
closedLazyInitializationException (LIE) in portal/taxon/{uuid}
100%
Description
org.hibernate.LazyInitializationException: could not initialize proxy - no Session
at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:148)
at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:266)
at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:68)
at eu.etaxonomy.cdm.model.agent.TeamOrPersonBase_$$_jvst503_6e.getNomenclaturalTitle(TeamOrPersonBase_$$_jvst503_6e.java)
at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getAuthorAndExAuthor(TaxonNameDefaultCacheStrategy.java:254)
at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getNonCacheAuthorshipCache(TaxonNameDefaultCacheStrategy.java:196)
at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getAuthorshipCache(TaxonNameDefaultCacheStrategy.java:170)
at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getTaggedTitle(TaxonNameDefaultCacheStrategy.java:411)
at eu.etaxonomy.cdm.model.name.TaxonName.getTaggedName(TaxonName.java:1477)
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)
at net.sf.json.JSONObject.fromObject(JSONObject.java:172)
at eu.etaxonomy.cdm.remote.json.processor.bean.HibernateProxyBeanProcessor.processBean(HibernateProxyBeanProcessor.java:28)
at net.sf.json.JSONObject._fromBean(JSONObject.java:676)
at net.sf.json.JSONObject.fromObject(JSONObject.java:172)
at net.sf.json.AbstractJSON._processValue(AbstractJSON.java:274)
at net.sf.json.JSONObject._processValue(JSONObject.java:2655)
at net.sf.json.JSONObject.processValue(JSONObject.java:2721)
at net.sf.json.JSONObject.element(JSONObject.java:1786)
at eu.etaxonomy.cdm.remote.json.processor.bean.AbstractBeanProcessor.processBean(AbstractBeanProcessor.java:149)
at net.sf.json.JSONObject._fromBean(JSONObject.java:676)
at net.sf.json.JSONObject.fromObject(JSONObject.java:172)
at eu.etaxonomy.cdm.remote.view.JsonView.render(JsonView.java:128)
at eu.etaxonomy.cdm.remote.view.JsonView.render(JsonView.java:188)
Updated by Andreas Kohlbecker about 4 years ago
- Category changed from cdmlib to cdmlib-remote
- Assignee changed from Andreas Müller to Andreas Kohlbecker
Updated by Andreas Müller about 4 years ago
The above error leads to the message "taxon does not exist" in the dataportal. This is incorrect error handling. The message should only appear if the webservice returns http 404. Otherwise we need a message that makes clear that an error occurred.
Updated by Andreas Kohlbecker about 4 years ago
Andreas Müller wrote:
The above error leads to the message "taxon does not exist" in the dataportal. This is incorrect error handling. The message should only appear if the webservice returns http 404. Otherwise we need a message that makes clear that an error occurred.
Yes, I know. This related to #2711 which is an open issue for years.
Updated by Andreas Kohlbecker about 4 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdmlib|7e76406ea76d8a95b7cbb718f23970cb7581443a.
Updated by Andreas Kohlbecker about 4 years ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
issue is fixed, this is confirmed by the fact that the LIE no longer occures: http://test.e-taxonomy.eu/cdmserver/caryo_spp/portal/taxon/b15ec01d-b909-4143-b197-e752b6f34d5b.json?subtree=876aa727-dc51-4912-8b19-1368303318bd (before the fix the LIE was also reproducible at the test server)