[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-985) Sessions created via SessionFactory.openSession(Connection) have invalid timestamp

[Steve Ebersole (JIRA)]

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

Steve Ebersole closed HHH-985.
------------------------------


Closing stale resolved issues

> Sessions created via SessionFactory.openSession(Connection) have invalid timestamp
> ----------------------------------------------------------------------------------
>
>                 Key: HHH-985
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-985
>             Project: Hibernate Core
>          Issue Type: Bug
>    Affects Versions: 3.0.5
>         Environment: 3.0.5
> MySql
>            Reporter: Patrick Casey
>
> Create Two sessions:
> Session s = HibHelper.getSessionFactory().openSession();	
> Session temp = HibHelper.getSessionFactory().openSession(s.connection());
> temp is a child of s in that it's using the same connection.
> Session s gets a proper timestamp : 4619002056560640
> Session temp gets an arbitrarily negative one: -9223372036854775808
> This means that anything you do via temp will fail when it tries to use the secondary cache because every entity in the cache will fail "freshness" relative to temp's timestamp.
> I'd think temp should either get its own timestamp based on its creation or inherit it's parten't timestamp. The large negative default value though means I can't use a derived session and the L2 cache :(.

-- 
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