openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-230) Handle guaranteed delivery of Data Cache events on normal JVM termination using TCPRemoteCommitProvider
Date Fri, 27 Apr 2007 21:12:15 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Linskey updated OPENJPA-230:
------------------------------------

    Attachment: OPENJPA-230.patch

It'd be nice to not have to synchronize. What about if we made the threads non-daemon, and
just call setRunning(false) instead? See attached (completely-untested) patch.

Also, I think that that boolean should be volatile to ensure thread-safety.

> Handle guaranteed delivery of Data Cache events on normal JVM termination using TCPRemoteCommitProvider
> -------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-230
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-230
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7
>            Reporter: Vikram Bhatia
>            Priority: Minor
>         Attachments: OPENJPA-230.patch, soln.diff
>
>
> When an application is commiting a transaction and then terminating, often not all events
regarding Data Cache are dispatched by the TCPRemoteCommitProvider. It seems that the JVM
on termination is not waiting until TCPRemoteCommitProvider has dispatched all events regarding
Data Cache. In this way some cache synchronization is lost.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message