[NXP-2781] Compass parameter compass.transaction.lockTimeout must be set to zero when its backend is PostgreSQL - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: None

Tags:
Impact type:

Configuration format change
Upgrade notes:

Hide

If compass backend is PostgreSQL, lockTimeout must set to zero in compass.cfg.xml:
<transaction commitBeforeCompletion="true" lockTimeout="0"
factory="org.compass.core.transaction.JTASyncTransactionFactory">
...
</transaction>

Show
If compass backend is PostgreSQL, lockTimeout must set to zero in compass.cfg.xml: <transaction commitBeforeCompletion="true" lockTimeout="0" factory="org.compass.core.transaction.JTASyncTransactionFactory"> ... </transaction>

Description

PostgreSQL allow only zero value for setQueryTimeout.
By default, compass 1.1.1 set it to 10s if no value is given for compass.transaction.lockTimeout in compass.cfg.xml

Error is: nested exception is org.postgresql.util.PSQLException: Method org.postgresql.jdbc3.Jdbc3Statement.setQueryTimeout(int) is not yet implemented.

Attachments

Activity

People

Assignee:

Julien Carsique

Reporter:

Julien Carsique

Participants:

Julien Carsique

Votes:

0 Vote for this issue

Watchers:

0 Start watching this issue

Dates

Created:

2008-10-28 18:07

Updated:

2008-10-28 18:22

Resolved:

2008-10-28 18:22

Time Tracking

Estimated:

30m

Remaining:

30m

Logged:

Not Specified