Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1316#issuecomment-206724794
I can't think of a reason of why would such a message be sent to storm from
outside the cluster. Ideally only cluster machines and daemons should have
access to the worker ports. Or if it indeeds needs to be solved, then a better
method would be to ignore the zero length payload and not add `new
TaskMessage(task, null)`. Before you make any change, let's wait for comments
from someone who is more familiar with this part of code.
---
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.
---
