[ https://issues.apache.org/jira/browse/STORM-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14528477#comment-14528477 ]
ASF GitHub Bot commented on STORM-809: -------------------------------------- GitHub user revans2 opened a pull request: https://github.com/apache/storm/pull/544 STORM-809: opology.message.timeout.secs should not allow null or <= 0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/revans2/incubator-storm STORM-809 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/storm/pull/544.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #544 ---- commit 998383ffe58834c52ab7ecdda668681177131cd4 Author: Robert (Bobby) Evans <ev...@yahoo-inc.com> Date: 2015-05-05T14:02:53Z STORM-809: opology.message.timeout.secs should not allow null or <= 0 ---- > topology.message.timeout.secs should not allow for null or <= 0 values > ---------------------------------------------------------------------- > > Key: STORM-809 > URL: https://issues.apache.org/jira/browse/STORM-809 > Project: Apache Storm > Issue Type: Bug > Reporter: Robert Joseph Evans > Assignee: Robert Joseph Evans > > topology.message.timeout.secs has bad things happen if it is set to null or > <= 0. If it is null killing or rebalancing a topology without providing a > timeout results in an NPE. <= 0 causes other periodic things to run too > frequently. -- This message was sent by Atlassian JIRA (v6.3.4#6332)