Commit 30f6efa3 authored by Misagh Moayyed's avatar Misagh Moayyed
Browse files

Update JPA-Ticket-Registry.md

parent 0aa46788
......@@ -117,21 +117,20 @@ registries for higher availability.</p></div>
{% endhighlight %}
- Configure other JPA dependencies:
##Cleaner Locking Strategy
The above shows a JPA 2.0 implementation of an exclusive, non-reentrant lock,
`JpaLockingStrategy`, to be used with the JPA-backed ticket registry.
This will configure the cleaner with the following defaults:
* tableName = "LOCKS"
* uniqueIdColumnName = "UNIQUE_ID"
* applicationIdColumnName = "APPLICATION_ID"
* expirationDataColumnName = "EXPIRATION_DATE"
* platform = SQL92
* lockTimeout = 3600 (1 hour)
| Field | Default
|-----------------------------------+---------------------------------------+
| `tableName` | `LOCKS`
| `uniqueIdColumnName` | `UNIQUE_ID`
| `applicationIdColumnName` | `APPLICATION_ID`
| `expirationDataColumnName` | `EXPIRATION_DATE`
| `platform` | SQL92
| `lockTimeout` | 3600 (1 hour)
# Database Configuration
......@@ -218,7 +217,7 @@ for information only and may serve as a reasonable starting point for configurin
<div class="alert alert-info"><strong>Usage Tip</strong><p>Note the health check query is specific to PostgreSQL.</p></div>
{% highlight bash %}
{% highlight properties %}
# == Basic database connection pool configuration ==
database.dialect=org.hibernate.dialect.PostgreSQLDialect
database.driverClass=org.postgresql.Driver
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment