1.0

Table Of Contents
sqlre.Prex
enable-tx-wait-mode
Uses lock waiting mode instead of the default "fail-fast" conict mode for transactions. In lock waiting
mode, a committed transaction is serialized and waits for other ongoing transactions instead of
conicting with those transactions.
Description
falseDefault Value
connectionProperty Type
sqlre.Prex
enforce-unique-host
Boolean that determines whether SQLFire puts redundant copies of the same data in different members
running on the same physical machine. By default, SQLFire tries to put redundant copies on different machines,
Description
but it puts them on the same machine if no other machines are available. Setting this property to true prevents
this and requires different machines for redundant copies.
falseDefault Value
connection (boot)Property Type
gemre.Prex
gemfire.WRITE_LOCK_TIMEOUT
The time to wait before throwing a conict exception (X0Z02) for a write-write conict that is detected between two
transactions. If the rst transaction that acquired the lock on the conicting row completes in this period of time (for
Description
example, it commits or aborts) then no conict occurs. However, keep in mind that SQLFire does not have any built-in
mechanism for detecting distributed deadlocks, so setting this property too high can cause two interlocked transactions
to both block for that period of time. Keep this timeout value small, because increasing the value can have a negative
impact on the overall throughput of a system that has transactions that perform lots of DML. The default value is 0,
which means that the system throws a conict immediately when it is detected.
If you change this property, set it to the same value on every data store member in your distributed system.
This property congures conict detection for READ_COMMITTED and REPEATABLE_READ transactions. See
Supported Transaction Isolation Levels on page 138.
0Default Value
systemProperty Type
n/aPrex
gemfire.READ_LOCK_TIMEOUT
The time to wait before throwing a conict exception (X0Z02) for a write-read conict that is detected between two
REPEATABLE_READ transactions. If the read lock acquired by the transaction that has read the conicting row
Description
completes in this period of time (for example, it commits or aborts) then no conict occurs for the transaction that is
writing the row. However, keep in mind that SQLFire does not have any built-in mechanism for detecting distributed
deadlocks, so setting this property too high can cause two interlocked transactions to both block for that period of time.
vFabric SQLFire User's Guide308
vFabric SQLFire Reference