[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5944) Refresh of an entity should clear its entries in the action queue

[Strong Liu (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44011#comment-44011 ] 

Strong Liu commented on HHH-5944:
---------------------------------

Jonas,

no, that's is not 'too much effort/risk' but design.
that's how we design Session, it is a light weight Object, and should be throw away once there is a hibernate exception thrown.

> Refresh of an entity should clear its entries in the action queue
> -----------------------------------------------------------------
>
>                 Key: HHH-5944
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5944
>             Project: Hibernate Core
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 3.3.2
>         Environment: JBoss 4.2.3
> Spring 2.5.5
>            Reporter: Jonas Olsson
>            Assignee: Strong Liu
>
> We're using optimistic locking for some statistics entities and are doing re-tries on StaleObjectStateException by refreshing the entity and re-applying our update. However, this fails in the same way every time as the failed update lingers in the action queue and is flushed before the changed update.
> Shouldn't/Couldn't refresh clear the action queue from actions of the given entity? As it is now it's quite nasty as you think you know what the instance looks like, but there is a hidden update just waiting for a flush.
> Our work-around is to cast Session to EventSource and clear the action queue ourselves (we pre-flush the session before the optimistic locking update to ensure the failed update is the only one queued), but that feels a bit like a hack. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira