Project

General

Profile

bug #8866

LazyInitializationException (LIE) in portal/taxon/{uuid}

Added by Andreas Kohlbecker about 1 month ago. Updated 19 days ago.

Status:
Closed
Priority:
Highest
Category:
cdmlib-remote
Target version:
Start date:
02/28/2020
Due date:
% Done:

100%

Severity:
critical
Found in Version:

Description

http://api.cybertaxonomy.org/caryophyllales_spp/portal/taxon/b15ec01d-b909-4143-b197-e752b6f34d5b.json?subtree=876aa727-dc51-4912-8b19-1368303318bd

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)

Associated revisions

Revision 7e76406e (diff)
Added by Andreas Kohlbecker 20 days ago

fix #8866 fixing incorrect bean initialization which has been indruduced during ref #7745

History

#1 Updated by Andreas Kohlbecker about 1 month ago

  • Category changed from cdmlib to cdmlib-remote
  • Assignee changed from Andreas Müller to Andreas Kohlbecker

#2 Updated by Andreas Müller about 1 month 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.

#3 Updated by Andreas Kohlbecker about 1 month 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.

#4 Updated by Andreas Kohlbecker 20 days ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50

#5 Updated by Andreas Kohlbecker 19 days 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)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)