Recover(Invokes) Thread in BPEL Console

Question

Hi,
Could anyone please explain what instances in a Recover(Invoke) Tab mean. It would be better if you could post link for any documentation.

Answer 1

Hi,
I don't understand this behaviour in detail, by now. Could you please state if this is correct?
1. I call an async bpel process A.
2. The message is put in the delivery queue.
3. My client is free again, not blocking.
4. Process A does not show up in Console by now. (If I would call checkpoint(), it would do).
5. A worker takes the message and instantiates the Process A.
6. Process A instance is running now, calling some sync processes.
7. NO dehydration so far.
8. Process A does not show up in Console by now. The called subprocess (sync) do show up, if they are completed.
9. Loop to 6, until Process A ends and makes callback to client.
10. After sending callback, Process A shows up in Console.
11. Now I can monitor, what HAS happened.
I understand, that you can't commit your process data, until a regular dehydration point is reached.
But consequence: I can't even SEE that there exists a process instance from A, until it worked through all the steps above. I just see a swarm of sub processes without an existing parent.
That's the behaviour, you call "intended"?
Workaround would be to do dehydration after each bpel invoke activity. Do you see a problem in doing this?
Thanks in advance!
Torsten