[jbossts-issues] [JBoss JIRA] (JBTM-1732) Durable STM instances require explicit sync to save state

Michael Musgrove (JIRA) issues at jboss.org
Tue Nov 21 09:42:00 EST 2017


     [ https://issues.jboss.org/browse/JBTM-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove updated JBTM-1732:
-----------------------------------
        Status: Resolved  (was: Pull Request Sent)
    Resolution: Done


> Durable STM instances require explicit sync to save state
> ---------------------------------------------------------
>
>                 Key: JBTM-1732
>                 URL: https://issues.jboss.org/browse/JBTM-1732
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>          Components: STM
>    Affects Versions: 5.0.0.M3
>            Reporter: Mark Little
>            Assignee: Michael Musgrove
>            Priority: Optional
>
> As with TXOJ, a persistent STM object isn't written to disk until a write lock is acquired on it within the scope of a transaction. Consider automating this at creation time.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jbossts-issues mailing list