E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (2)
View Page History
...
The container configuration is located into the file {{server.properties}} and expressed as property (key/value): | {{petals.topology.url}} | If the container configuration, ie. {{server.properties}}, is defined by a file-based URL, the default value is {{topology.xml}} in the same directory than the container configuration. Otherwise, no default value is defined and a value *MUST* be provided. | URL of the [topology definition|Topology Configuration]. |
| {{petals.topology.passphrase}} | {{petals}} | Pass-phrase used as security to get sensible information of other Petals nodes of the topology as JMX credentials from this node. |
| {{petals.topology.passphrase}} | {{petals}} | Pass-phrase used as security to get sensible information of other Petals nodes of the topology as JMX credentials from this node. |
|| Router || || ||
| {{petals.router.strategy}} | {{highest,3,2,1}} | The strategy of the router. |
| {{petals.router.send.attempt}} | {{2}} | Defines the number of attempt to send a message to an endpoint. Several attempts can be done when there is transport failure during the convey of a message. |
| {{petals.router.send.delay}} | {{1000}} | The delay, in milliseconds, between the send attempts. |
| {{petals.router.strategy}} | {{highest,3,2,1}} | The strategy of the router. |
| {{petals.router.send.attempt}} | {{2}} | Defines the number of attempt to send a message to an endpoint. Several attempts can be done when there is transport failure during the convey of a message. |
| {{petals.router.send.delay}} | {{1000}} | The delay, in milliseconds, between the send attempts. |
|| Transporter || || ||
| {{petals.transport.queue.max-size}} | {{10000}} | Queue size, in message number, of the message exchange transporter. If the queue is full, new message exchange can rejected. |
| {{petals.transport.queue.max-size}} | {{10000}} | Queue size, in message number, of the message exchange transporter. If the queue is full, new message exchange can rejected. |
...| {{petals.transport.tcp.send.evictor.delay}} | {{60000}} | The delay, in milliseconds, before running the eviction thread removing unused message exchange senders. |
| {{petals.transport.tcp.send.evictable.delay}} | {{60000}} | The delay, in milliseconds, before an idle 'message exchange sender' is set evictable. |
| {{petals.transport.tcp.send.evictable.delay}} | {{60000}} | The delay, in milliseconds, before an idle 'message exchange sender' is set evictable. |
|| Persistence Service || || ||
| {{petals.persistence.duration}} | {{3600000}} | The duration, in milliseconds, of temporary persisted data, such as Message Exchange. |
| {{petals.persistence.fetch-size}} | {{10}} | The persistence SQL request fetch size, in rows. |
| {{petals.persistence.duration}} | {{3600000}} | The duration, in milliseconds, of temporary persisted data, such as Message Exchange. |
| {{petals.persistence.fetch-size}} | {{10}} | The persistence SQL request fetch size, in rows. |
Other parameters associated to Petals ESB extensions can be found in the file {{server.properties}}:
...