Github user liurenjie1024 commented on the pull request:
https://github.com/apache/storm/pull/1316#issuecomment-206732733
The reason why such a message is sent is that our security team is scanning
all the ports listened on each server and tries to detect potential weakness.
At first thought I just wanted to ignore messages with zero payload, but I
think ignoring messages failed to be deserialized would be more robust. I think
this also matches storm's design since it throws away messages whose target
task id is not in the worker and this patch is just a complement.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
