[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-3256) OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-3256.
-------------------------------

    Resolution: Rejected

No it should not.  See my comment on the linked issue.

> OptimizerFactory$PooledOptimizer.generate doesn't set keep the in-memory hi_value in sync with the db next_val (after a JBoss restart)
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-3256
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3256
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.2.6
>         Environment: Hibernate 3.2.6, MySQL 5
>            Reporter: Tom Muldoon
>
> After a JBoss restart, the in-memory hiValue is -1.  As such, the callback.getNextValue( ) method is invoked twice.  With an increment size of 50 and a current database next_val of 10000, the PooledOptimizer.generate method returns a value of 10000 (as expected) and sets the in memory hiValue to 10050 (also as expected), however, it sets the db next_val to 10100. Shouldn't the db next_val be kept in sync with the in-memory hiValue (i.e. 10050)?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira