4 Replies Latest reply on Jan 26, 2010 7:02 PM by jivicari

    fail-safe cleanup (collections)

    sherkan777

      Hi,
      Can anybody help me and tell why still I get this? I don't know in which cases this is thrown. Each time when this happen my em clear db entities.


      2008-04-22 21:44:09,050 WARN  [org.hibernate.engine.loading.LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@79eafff0<rs=org.postgresql.jdbc3.Jdbc3ResultSet@95e2493>


        • 1. Re: fail-safe cleanup (collections)
          toby.tobias.hill.gmail.com

          We also get these a lot after our upgrade to seam 2.1.0.GA.


          Unfortunately it does not help upgrading the hiberate.jar to the latest version either (I did this since there are indications in the HHH-Jira that this printout is a bug which has been fixed in later versions).

          • 2. Re: fail-safe cleanup (collections)
            toby.tobias.hill.gmail.com

            Actually I was wrong. This message (which we also got alot of recently) has nothing to do with Seam 2.1.0.GA as I suggested above. You see, at the same time as I changed seam versions I also made a minor change to one of our annotations.


            I made a collection EAGER as this:


                @OneToMany(mappedBy = "company", cascade = ALL, fetch = EAGER)
            



            This gave the warning in our logs.


            If also adding


                @Fetch(value = SELECT)
            


            ... the error goes away. I doubt that this is a SEAM-bug. I would guess Hibernate.

            • 3. Re: fail-safe cleanup (collections)
              kamrul
              My Warring Message is like bellow: What should I do?

              WARN  [LoadContexts] fail-safe cleanup (collections) : org.hibernate.engine.loading.CollectionLoadContext@c84d9d<rs=oracle.jdbc.driver.OracleResultSetImpl@16903c0>
              • 4. Re: fail-safe cleanup (collections)
                jivicari

                The problem I think is from hibernate when you fetch a collection without elements, if you insert an element in the collection the problem dissapear. Try it to verify that.


                I read somewhere that it is a bug in hibernate and it was solved in hibernate 3.2.6 a higher. I hope it helps you and forgive my english.