Page History
| Div | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
| Multiexcerpt include | ||||||
|---|---|---|---|---|---|---|
|
...
This construct of a conversation is implemented by two elements: a signal and a conversationID. The waiting service waits for a specific signal sent by the conversation partner. This signal is identified by the signal name and the conversationID, that can be passed as a parameter to each signal action.
| Info | ||
|---|---|---|
| ||
The conversation ID will be logged as correlation ID to the transaction log for send signal actions and accept event actions (see Contents of the Transaction Log). |
The conversations are persisted in a persistent state database. If you stop a service or the service crashes between sending and accepting, the service will try to complete the conversation after service restart. Nevertheless, the accept event timeouts continue counting down and is considered after service restart.
If you use an external persistent state database, multiple services with same persistent state owner can send conversation signals between each other.
...
Overview
Content Tools