E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (5)
View Page History
...
{center}{*}Configuration of the component, CDK part*{center} || {color:#333333}Parameter{color} || {color:#333333}Description{color} || {color:#333333}Default{color} || {color:#333333}Required{color} || Scope ||
| acceptor-pool-size | The size of the thread pool used to accept Message Exchanges from the NMR. Once a message is accepted, its processing is delegated to the processor pool thread. | {center}3{center}\\ | {center}Yes{center}\\ | {center}Runtime{center}\\ |
| acceptor-pool-size | The size of the thread pool used to accept Message Exchanges from the NMR. Once a message is accepted, its processing is delegated to the processor pool thread. | {center}3{center}\\ | {center}Yes{center}\\ | {center}Runtime{center}\\ |
| acceptor-retry-number | Number of tries to submit a message exchange to a processor for processing before to declare that it cannot be processed. | {center}40{center}\\ | {center}No{center}\\ | {center}Installation{center}\\ |
| acceptor-retry-wait | Base duration, in milliseconds, to wait between two processing submission tries. At each try, the new duration is the previous one added by this base duration multiplied by the try number plus a random value between 0 and 10. | {center}250{center}\\ | {center}No{center}\\ | {center}Installation{center}\\ |
| acceptor-stop-max-wait | The max duration (in milliseconds) of the stop of an acceptor before to force it to stop. | {center}500{center}\\ | {center}No{center}\\ | {center}Runtime{center}\\ |
| message-processor-max-pool-size | Max size of the object pool containing message exchange processors. | {center}{{processor-max-pool-size}}{center}\\ | {center}No{center}\\ | {center}Runtime{center}\\ |
| acceptor-retry-wait | Base duration, in milliseconds, to wait between two processing submission tries. At each try, the new duration is the previous one added by this base duration multiplied by the try number plus a random value between 0 and 10. | {center}250{center}\\ | {center}No{center}\\ | {center}Installation{center}\\ |
| acceptor-stop-max-wait | The max duration (in milliseconds) of the stop of an acceptor before to force it to stop. | {center}500{center}\\ | {center}No{center}\\ | {center}Runtime{center}\\ |
| message-processor-max-pool-size | Max size of the object pool containing message exchange processors. | {center}{{processor-max-pool-size}}{center}\\ | {center}No{center}\\ | {center}Runtime{center}\\ |
| processor-pool-size | The size of the thread pool used to process Message Exchanges. Once a message is accepted, its processing is delegated to one of the thread of this pool. | {center}10{center} | {center}Yes{center}\\ | {center}Runtime{center} |
| processor-max-pool-size | The maximum size of the thread pool used to process Message Exchanges. The difference between this size and the processor-pool-size represents the dynamic threads that can be created and destroyed during overhead processing time. \\ | {center}50{center}\\ | {center}No{center} | {center}Runtime{center}\\ |
| notifications | Enable the notifications mode. The component produces and consumes generic notifications when receiving and sending messages. See the Petals View documentation for further details. \\ | {center}false{center}\\ | {center}No{center}\\ | {center}Installation{center}\\ |
| notif-retry-policy-min | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Delay before the first notification retry is attempted, in second. \\ | {center}1{center} | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-max | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The maximum delay value authorized, in second. | {center}60{center} | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-factor | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The factor applies on the previous attempt, for each new attempt. \\ | {center}2{center}\\ | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-nb | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Number of retry once the maximum delay value is reached. \\ | {center}1000{center}\\ | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-min | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Delay before the first notification retry is attempted, in second. \\ | {center}1{center} | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-max | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The maximum delay value authorized, in second. | {center}60{center} | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-factor | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
The factor applies on the previous attempt, for each new attempt. \\ | {center}2{center}\\ | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| notif-retry-policy-nb | The notification retry policy is triggered if the notification component is not reachable at the starting of the component. \\
Number of retry once the maximum delay value is reached. \\ | {center}1000{center}\\ | {center}bounds to notifications{center} | {center}Installation{center}\\ |
| processor-keep-alive-time | When the number of processors is greater than the core, this is the maximum time that excess idle processors will wait for new tasks before terminating, in seconds. \\ | {center}300{center}\\ | {center}No{center} | {center}Runtime{center}\\ |
| processor-stop-max-wait | The max duration (in milliseconds) of message exchange processing on stop phase.\\ | {center}15000{center}\\ | {center}No{center} | {center}Runtime{center}\\ |
| time-beetween-async-cleaner-runs | The time (in milliseconds) between two runs of the asynchronous message exchange cleaner.\\ | {center}2000{center}\\ | {center}No{center} | {center}Installation{center}\\ |
| processor-stop-max-wait | The max duration (in milliseconds) of message exchange processing on stop phase.\\ | {center}15000{center}\\ | {center}No{center} | {center}Runtime{center}\\ |
| time-beetween-async-cleaner-runs | The time (in milliseconds) between two runs of the asynchronous message exchange cleaner.\\ | {center}2000{center}\\ | {center}No{center} | {center}Installation{center}\\ |
| properties-file | Name of the file containing properties used as reference by other parameters. Parameters reference the property name in the following pattern $\{myPropertyName}. At runtime, the expression is replaced by the value of the property. \\
\\
\\
...* a file relative to the PEtALS installation path
* an empty value to stipulate a non-using file | {center}\-{center} | {center}No{center} | {center}Installation{center} |
* an empty value to stipulate a non-using file | {center}\-{center} | {center}No{center} | {center}Installation{center} |
| monitoring-sampling-period | Period, in seconds, of a sample used by response time probes of the monitoring feature.\\ | {center}300{center}\\ | {center}No{center} | {center}Installation{center}\\ |
{table-plus}