Configuration of the Message Processing Core Client properties
Cache expiration interval for trusted ca certificates
Default: -1
How long (in milliseconds) a request may wait for the trusted-certificate list to finish loading when it is not available yet, instead of immediately using the fallback store above. If loading keeps failing, waiting is automatically bypassed so requests are not delayed unnecessarily. Set to 0 to disable waiting (requests immediately use the fallback store, as in previous releases).
Default: 30000
Which trusted-certificate store the gateway uses while the up-to-date list is still being loaded or refreshed from Policy Manager (for example at startup, after a certificate change, or on the periodic refresh).
LAST_GOOD - keep using the last successfully loaded list until the new one is ready; if nothing has been loaded yet, use the built-in default CA certificates. (Recommended.)
BOOTSTRAP - always use the built-in default (JDK) CA certificates until the new list is ready.
LEGACY - do not use any interim store; restores the original (older) behaviour where the gateway depends on the fresh load and requests can fail if it cannot be loaded. Only choose this if you specifically do not want any fallback; it also brings back the original heavier load on the gateway when many requests arrive at once.
Default: LAST_GOOD
What other requests do when the list is already loaded but is being refreshed in the background (one thread is fetching the newer list).
NO_WAIT - do not wait; serve immediately using the fallback store selected by 'Trusted CA cert fallback mode' above (the last loaded list under LAST_GOOD, or the built-in default CA certificates under BOOTSTRAP).
WAIT - make the other requests wait for the refresh to finish (up to the initial-load wait time above) so they get the newly loaded list, instead of the slightly older one. If the wait time is exceeded they serve the fallback store (as in NO_WAIT).
Default: WAIT