-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
---
-
---
-
-
Running a process, elasticsearch gets events from TransactionalPersistenceEventManager, but some steps running the process are executed by TriggerUpdateTransactionSynchronization which is a drools manager, not aware of event emitters integration.
Sharing two examples that miss some events:
subprocess:
process with HT and subprocess, parent event and task are captured by event emitters, subprocess are missed:
here parent process calling subprocess. Subproces is captured but parent process is missed:
To detect missing parameters, enable org.apache and filter by:
grep http-outgoing server.log | grep _index
2022-11-15 16:47:34,791 DEBUG [org.apache.http.wire] (pool-927-thread-10) http-outgoing-22 >> "{ "update" :
{ "_index" : "tasks", "_type" : "task", "_id" : "default-kieserver_1264" } }[\n]"
2022-11-15 16:49:07,613 DEBUG [org.apache.http.wire] (pool-927-thread-11) http-outgoing-22 >> "{ "index" :
}[\n]"
2022-11-15 16:51:13,517 DEBUG [org.apache.http.wire] (pool-927-thread-12) http-outgoing-22 >> "{ "index" :
}[\n]"
2022-11-15 16:51:44,020 DEBUG [org.apache.http.wire] (pool-927-thread-12) http-outgoing-22 >> "{ "index" :
}[\n]"
2022-11-15 16:54:42,208 DEBUG [org.apache.http.wire] (pool-927-thread-13) http-outgoing-22 >> "{ "index" :
}[\n]"
on database process are like:
evaluation 665, only-scripts 666 but no 666 event appears.
- clones
-
RHPAM-4584 Some events are missed in event emitters (elastic search)
- Closed