corda.p2p.linkManager
Configuration schema for the P2P link manager.
heartbeatMessagePeriod
- The heartbeat message period in milliseconds.
Default value: 2000
Minimum value: 500
maxMessageSize
- The maximum message size in bytes.
Default value: 1000000
Minimum value: 1000
maxReplayingMessages
- The maximum number of replaying messages between two peers.
Default value: 100
Minimum value: 1
replayAlgorithm
- The algorithm used to schedule messages for replay.constant
- Replay messages at a constant rate.messageReplayPeriod
- The message replay period in milliseconds.
Default value: 2000
Minimum value: 500
exponentialBackoff
- Replay messages with capped exponential backoff.baseReplayPeriod
- The message replay period base in milliseconds.
Default value: 2000
Minimum value: 500
replayPeriodCutoff
- The message replay period cutoff in milliseconds.
Default value: 10000
Minimum value: 500
revocationCheck
- The type of revocation check for the session certificate.mode
This must be set to one of the following values:- SOFT_FAIL - The revocation check will succeed if the revocation status cannot be determined under certain circumstances. See java.security.cert.PKIXRevocationChecker.Option.SOFT_FAIL java doc for more details.
- HARD_FAIL - The opposite of SOFT_FAIL. This is the most rigorous check. Amongst other requirements, this check requires that the CRL checking URL is available on every level of certificate chain.
- OFF - Disables the CRL check.
sessionRefreshThreshold
- The session refresh threshold in seconds. The default value is five days.
Default value: 432000
Maximum value: 432000
sessionTimeout
- The session timeout in milliseconds.
Default value: 10000
Minimum value: 500
sessionsPerPeer
- The number of actively maintained sessions between two peers.
Default value: 4
Minimum value: 1
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.