AdministratorsPermanent link for this heading

As an administrator you can expect the following new features.

  • FSCOWS@1.1001:SendHttpSoapMessage checks the server certificate also on Microsoft Windows correctly.
  • Object locks
    • Expired object locks are now automatically removed from the COO service.
      • The locks are checked once per minute.
      • Locks expire after 480 seconds (COO_LOCK_TIMEOUT) by default.
      • The expiration of object locks can be disabled for normal locks with the COO_LOCK_AUTOEXPIRE option, but not for attribute locks and locks that are created during commit.
    • The undocumented COO service option COO_LOCK_FORCETIMEOUT has been removed.
    • The check of flags when breaking a lock has been tightened.
      • This affects objects that are permanently and normally locked at the same time.
      • Breaking a permanent lock requires TV_BREAKPERMLOCK.
      • Breaking a normal lock requires TV_BREAKLOCK.
      • Breaking a normal lock on an object that is permanently locked by another user requires TV_BREAKPERMLOCK, as this breaks the permanent lock.
      • Breaking a permanent lock on an object that is normally locked by the current user also requires TV_BREAKLOCK, as this breaks the user's normal lock.
    • Permanent locks can now only be unlocked using Commit.
  • To ensure that background tasks do not block the execution of other background tasks, a maximum runtime is defined. If the background task is not completed within the given period of time, the background task gets aborted by throwing the COOSYSTEM@1.1:COOERR_TIMEOUT error on every expression or method call.
    The maximum runtime depends on the specified duration:
    • Very Short (incl. variants): 10 minutes
    • Short (incl. variants): 15 minutes
    • Default (incl. variants): 30 minutes
      Note: Except DD_DEFAULT_RULES: 15 minutes
    • Long (incl. variants): 60 minutes
    • Very Long (incl. variants): no timeout
  • The EXECASYNCTIMEOUT environment variable defines the amount of time (in milliseconds) after which an expression which is started using COOSYSTEM@1.1:ExecAsync gets aborted by throwing the error COOSYSTEM@1.1:COOERR_TIMEOUT. Zero means that no timeout is enforced.
    Default value: 0 ms (disabled)
  • The FSCVEXT_REQUESTTIMEOUT environment variable defines the maximum duration (in milliseconds) after which a request gets aborted. Zero means that no timeout is enforced.
    Default value: 0 ms (disabled)
  • The new “Bulk Job Control” object class can reference a bulk job and overwrite values of the bulk job. Logging and related functionality are available directly on the bulk job control object.