You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Polovtcev (Jira)" <ji...@apache.org> on 2021/07/22 12:35:00 UTC
[jira] [Updated] (IGNITE-15178) Add validation of MessageGroup IDs
[ https://issues.apache.org/jira/browse/IGNITE-15178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Polovtcev updated IGNITE-15178:
-----------------------------------------
Description:
Currently message groups IDs are simply {{short}} values that are manually assigned to every module. This can lead to ID clashes which will lead to message handlers being invoked unexpectedly.
We should find a way to validate group IDs across all modules. One way is to check that message group classes are the same when a handler is registered in the {{MessagingService}}.
was:
Currently message groups IDs are simply {{short}} values that are manually assigned for every module. This can lead to ID clashes which will lead to message handlers being invoked unexpectedly.
We should find a way to validate group IDs across all modules. One way is to check that message group classes are the same when a handler is registered in the {{MessagingService}}.
> Add validation of MessageGroup IDs
> ----------------------------------
>
> Key: IGNITE-15178
> URL: https://issues.apache.org/jira/browse/IGNITE-15178
> Project: Ignite
> Issue Type: Task
> Components: networking
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Major
> Fix For: 3.0.0-alpha3
>
>
> Currently message groups IDs are simply {{short}} values that are manually assigned to every module. This can lead to ID clashes which will lead to message handlers being invoked unexpectedly.
> We should find a way to validate group IDs across all modules. One way is to check that message group classes are the same when a handler is registered in the {{MessagingService}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)