Property

Description

Transaction logs settings

Transactions can be stored either directly or delayed for better performance. The following properties are used for logging:

  • TRANSACTION_LOG_COLUMNS = ResponseStatus,RequestTime,ResponseTime,Request,Response,RelyingPartyId,RelyingPartyIp,RelyingPartySslCert,ErrorCode
    Inspection System Transactions log columns to be stored in the database to keep the database growth under control. Default value: ResponseStatus,RequestTime,ResponseTime,Request,Response,RelyingPartyId,RelyingPartyIp,RelyingPartySslCert,ErrorCode
  • TRANSACTION_LOG_MODE = LAZY
    Used to decide whether the transactions are kept in memory before these are stored in the database (LAZY logging) or directly stored in the database (EAGER logging). Default value: LAZY; Possible values: LAZY, EAGER <br>In case of LAZY logging the transaction logs are kept in memory upto the number of seconds configured in TRANSACTION_LOG_LAZY_INTERVAL or number of transactions configured in TRANSACTION_LOG_LAZY_RECORD_COUNT whichever is reached first.
  • TRANSACTION_LOG_LAZY_INTERVAL = 2
    When LAZY logging is configured, transactions are kept in memory upto the configured time or if the configured TRANSACTION_LOG_LAZY_RECORD_COUNT is reached before it Default value: 2 seconds
  • TRANSACTION_LOG_LAZY_RECORD_COUNT = 50
    When LAZY logging is configured, transactions are kept in memory until the configured number of transactions is reached or if the configured. TRANSACTION_LOG_LAZY_INTERVAL is met before it. Default value: 50.


See also

Signing Service

Verification Service
OCSP Service

OCSP Repeater
Certification Service
CRL Monitor
TSA Service
OCSP Monitor
GoSign Service
SAM Service
RAS Service
Unity Service
HMAC Service

Inspection System Service
CSP Service