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

Mark Little (JIRA) issues at jboss.org
Mon May 11 03:03:19 EDT 2015

    [ https://issues.jboss.org/browse/JBTM-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066741#comment-13066741 ] 

Mark Little commented on JBTM-1732:

Adding for completeness: the workaround (as with TXOJ) is to force write the state prior to any other users (threads, cloned instances or processes) using the object.

> 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: Mark Little
>            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

More information about the jbossts-issues mailing list