知识卡片
先到消息需要缓冲
BPMN标准关联要求实例在消息到达时已经等待接收。外部服务的异步回复可能比调用确认处理和本地提交更快,因此看监控时实例已等待,先前关联却曾报错。引擎提供带TTL缓冲时,可在实例就绪后匹配;否则依赖消息系统重投关联。固定睡眠只能验证竞态,不能成为可靠方案。
结构图:
sequenceDiagram
participant P as 流程
participant S as 外部服务
participant B as 消息缓冲
P->>S: 请求
S-->>B: 快速回复
P->>P: 提交接收等待状态
B-->>P: 实例就绪后关联
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 工作流引擎与集成挑战 · 查看原书依据
The BPMN standard defines message correlation in such a way that a process instance needs to be ready to receive that specific message at the exact time the message arrives. So, strictly speaking, when no token for a specific process instance is waiting in the receive task, incoming messages cannot be correlated and are dumped.
参考来源
- 位置:《Practical Process Automation》第9章《工作流引擎与集成挑战》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch09.xhtml)
- 结论依据:原文给出的机制、实例与边界支持本卡的解释。
- 原始内容:The BPMN standard defines message correlation in such a way that a process instance needs to be ready to receive that specific message at the exact time the message arrives. So, strictly speaking, when no token for a specific process instance is waiting in the receive task, incoming messages cannot be correlated and are dumped.