A Transactional WFS (WFS-T) client can lock features through the LockFeature and GetFeatureWithLock requests, to get exclusive access to modify or delete them. When requesting such a lock, a client can specify an EXPIRY value that determines how long the lock is held.

The OGC WFS specification doesn’t define a standardized maximum for this value, so a client could in theory request a lock that stays valid for days, weeks, or even longer, blocking other users from editing the affected features for that entire period.

To prevent such a long-lasting lock, LuciadFusion limits how long a requested lock can be held. By default, a lock expires after one day at most, but you can change this limit.

Configure the maximum lock expiry time

To change the maximum WFS-T lock expiry time, set the wfs.maxLockExpiry property under fusion.ogc in the config/fusion.common.yml file: 

fusion.ogc:
  # Maximum expiry time, in seconds, for a WFS-T feature lock requested through LockFeature or GetFeatureWithLock.
  # Defaults to no expiry if not set.
  # LuciadFusion configures this to 86400 (1 day) by default.
  wfs.maxLockExpiry: 86400

Restart LuciadFusion for the change to take effect.

If a client requests a lock expiry value that exceeds this limit, the request is rejected with an InvalidParameterValue service exception report. The configured limit is also advertised as a maxExpiry constraint on the LockFeature and GetFeatureWithLock operations in the WFS GetCapabilities response, so that clients can find out about it up front.