You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Subject | Property | Default | Explanation | Property file | Additional information |
---|---|---|---|---|---|
Aggregates | blueriq.customerdata-client.list.record.limit | 10 | Maxiumum results of the search. |
| |
blueriq.customerdata-client.url | Url for the customerdata service |
| |||
blueriq.customerdata-client.username | Username used for authentication against the customerdata service |
| |||
blueriq.customerdata-client.password | Password used for authentication against the customerdata service |
| |||
blueriq.customerdata-client.preemptive-authentication | true | Use preemptive authentication |
| since 11.8 | |
blueriq.customerdata-client.socket-timeout | 120 (seconds) | Time waiting for data – after establishing the connection; maximum time of inactivity between two data packets |
| Note: exception thrown can still cause data changes on Customer Data Service side, because connection has been established. | |
blueriq.customerdata-client.connection-timeout | 10 (seconds) | Time to establish the connection with the remote host |
| ||
blueriq.customerdata-client.connection-request-timeout | 10 (seconds) | Time to wait for a connection from the connection manager/pool |
| https://hc.apache.org/httpclient-legacy/preference-api.html | |
blueriq.customerdata-client.pool.validate-after-inactivity | 2500 (milliseconds) | Defines period of inactivity in milliseconds after which persistent connections must be re-validated prior to being leased to the consumer. Non-positive value passed to this method disables connection validation. This check helps detect connections that have become stale (half-closed) while kept inactive in the pool. |
| ||
blueriq.customerdata-client.pool.default-max-per-route | 50 | The default maximum number of concurrent connections per route |
| ||
blueriq.customerdata-client.pool.max-total | 1000 | The maximum total connections |
|