Forced Rollback - Space Schema

Added by Gilad David Maayan, last edited by Aleia Hutcherson on May 25, 2008  (view change)
  GigaSpaces 5.X

Documentation Home
Quick Start Guide
Release Notes

Previous release
  Search Here
Searching GigaSpaces Platform 5.X Documentation

                                               
Summary: Forcing a release of all locked transactions, when restarting a persistent space.

Overview

There are situations when persistent space is restarted and cannot connect to the Jini Transaction Manager. In such cases you may want to rollback all entries that are locked under the transaction.
Having <rollback_on_tm_failed> as true will unlock all locked entries to be accessible for clients.

<space-config>
           <!--if true all entries under transaction will be aborted, if the space failed to connect
            to Transaction Manager on WARM_INIT-->
           <rollback_on_tm_failed>false</rollback_on_tm_failed>
</space-config>

Wiki Content Tree

Your Feedback Needed!

We need your help to improve this wiki site. If you have any suggestions or corrections, write to us at techw@gigaspaces.com. Please provide a link to the wiki page you are referring to.

Labels

 
(None)