|
|
Re: [Model Semantics] Activate Event of Tasks with multipleTaskActivationLimit > 1 [message #1827128 is a reply to message #1826978] |
Thu, 07 May 2020 18:53   |
Benjamin Beichler Messages: 4 Registered: April 2020 |
Junior Member |
|
|
I think we completely agree. I think even your example could be modeled, if you have a bounded number of worker threads (which your answer might imply). Then each worker thread is a different task (with its own state) and you need some distribution logic (Round-Robin to all worker threads should be easily doable with some mode switch and counter).
Even modern system tend to not spawn dynamically threads for their activation (e.g. for web servers apache/nginx is a good example, where the actual request/response is generated by a limited thread pool).
Nonetheless, my actual question was already answered in another way, I was asking about the actual time point, where the activate event is generated. But since there exists also stimulus events, they mark the actual time point of triggering the process (in comparison to the activate event, which will be emitted, when the process can actually scheduled for execution).
Finally, I would suggest, that the multiple activation and therefore the stalled behavior of task activation is also documented in the meta model description/ app4mc help. The right person may open a low priority bug request at the right place :-)
|
|
|
|
Powered by
FUDForum. Page generated in 0.02150 seconds