Uploaded image for project: 'DSpace'
  1. DSpace
  2. DS-3775

Hibernate LazyInitializationException on submission completion under certain conditions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 6.0, 6.1, 6.2
    • Fix Version/s: 6.3
    • Component/s: XMLUI
    • Labels:
    • Attachments:
      0
    • Comments:
      9
    • Documentation Status:
      Not Required

      Description

      In 6.2 with XMLUI, when versioning is enabled in xmlui.xconf...

      When submitting an item to a Collection that has a logo bitstream, the following cocoon stack trace is displayed in the UI upon submission completion instead of the submission complete view:

      Java stacktrace: org.hibernate.LazyInitializationException: could not initialize proxy - no Session
          at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:165)
          at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:286)
          at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:185)
          at org.dspace.content.Bitstream_$$_jvstad0_3.getID(Bitstream_$$_jvstad0_3.java)
          at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:325)
          at org.dspace.app.xmlui.utils.DSpaceValidity.add(DSpaceValidity.java:280)
          at org.dspace.app.xmlui.aspect.versioning.Navigation.getValidity(Navigation.java:129)
          at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:483)
          at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
          at com.sun.proxy.$Proxy134.getValidity(Unknown Source)...

      The item is properly submitted. This seems to be purely presentational.

      Removing the logo from the collection works around the bug.

      Experimenting with setting the Collection Entity's logo property to be an EAGER join instead of lazy led to a similar No Session stack trace centered around a getName() call on the Bitstream entity.

      I haven't tested older 6x versions or JSPUI.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jsavell Jason Savell
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: