corda.db heading-link-icon

Configuration schema for the database section. Note that this configuration cannot be updated dynamically through the REST endpoint.

  • database - Database settings.
    • jdbc - JDBC settings.
      • directory - The directory that contains the JDBC drivers.
        Default value: /opt/jdbc-driver
      • driver - The JDBC driver.
        Default value: org.postgresql.Driver
      • url - The JDBC URL.
        Default value: jdbc:postgresql://cluster-db:5432/cordacluster
    • pass - The database password.
    • pool - Database pool settings.
      • idleTimeoutSeconds - The maximum time (in seconds) a connection can stay idle in the pool. A value of 0 means that idle connections are never removed from the pool.
        Default value: 120
        Minimum value: 0
      • keepaliveTimeSeconds - The interval time (in seconds) in which connections will be tested for aliveness. Connections which are no longer alive are removed from the pool. A value of 0 means this check is disabled.
        Default value: 0
        Minimum value: 0
      • maxLifetimeSeconds - The maximum time (in seconds) a connection can stay in the pool, regardless if it has been idle or has been recently used. If a connection is in-use and has reached "maxLifetime" timeout, it will be removed from the pool only when it becomes idle.
        Default value: 1800
        Minimum value: 1
      • max_size - The maximum database pool size.
        Default value: 10
        Minimum value: 1
      • min_size - The minimum database pool size. If left null will default to the `max_size` value.
        Default value:
      • validationTimeoutSeconds - The maximum time (in seconds) that the pool will wait for a connection to be validated as alive.
        Default value: 5
        Minimum value: 1
    • user - The database user.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.