topic Re: Hibernate AssertionFailure error when creating associations in Alfresco Archive

Hibernate AssertionFailure error when creating associations

lee — Thu, 26 Nov 2009 09:50:24 GMT

I don't get an AssociationExists error when I try to create an association that already exists. Instead, I get the following hibernate assertion failure:09:38:26,457 ERROR [org.hibernate.AssertionFailure#<init>] an assertion failure occured (this may indicate a bug in Hibernate, but is more li

Re: Hibernate AssertionFailure error when creating associations

lee — Thu, 26 Nov 2009 11:48:21 GMT

Here's the code I'm using btw:


try {
            log.debug("nPushing " + node);
            nodeService.createAssociation(env, node, CustomContentModel.ASSOC_UPDATED_CONTENT);
            
         } 
         catch (AssociationExistsException assocEx){
            log.debug(" – Association already exists");
         }
         catch(Exception ex) {
            log.debug("  –  FAILED");
         }
‍‍‍‍‍‍‍‍‍‍‍‍‍

I don't understand why the final catch doesn't seem to actually catch the hibernate exception.

Any suggestions?

Re: Hibernate AssertionFailure error when creating associations

dward — Sat, 01 May 2010 16:10:43 GMT

I ran the following unit test on 3.1.2, just to make sure that the AssociationExistsException is still being thrown as appropriate

org.alfresco.repo.node.BaseNodeServiceTest.testDuplicateAssociationDetection()

This unit test is run during every Alfresco build, so we simply wouldn't release a build without this functionality working.

Your stack trace would suggest that the flush() that's used by createAssociation() is flushing out another problem that's causing Hibernate to complain. Perhaps there was a previous error in the same transaction?

If you are still experiencing the problem, please provide a simple test case that reproduces the problem.

Thanks

Dave

Re: Hibernate AssertionFailure error when creating associations

derek — Tue, 04 May 2010 12:52:51 GMT

Hi,
With Hibernate, you can't catch a DAO-level exception and continue as normal; the Hibernate Session must be considered to be corrupted i.e. you need to handle the exception outside of your transaction and redo the transaction with an alternative approach. This is a function of Hibernate (as you can see from the flush exception you get) and will be avoidable when we run without Hibernate.
Regards