[ https://issues.apache.org/jira/browse/STORM-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201816#comment-14201816 ]
Sean T Allen commented on STORM-549: ------------------------------------ found the bug. the problem is this line expression: (not (storm-conf TOPOLOGY-ENABLE-MESSAGE-TIMEOUTS)) (storm-conf TOPOLOGY-ENABLE-MESSAGE-TIMEOUTS) is a java boolean AND... (not (Boolean. false)) == false correct logic is (if (or (system-id? (:component-id executor-data)) (and (= false (storm-conf TOPOLOGY-ENABLE-MESSAGE-TIMEOUTS)) (= :spout (:type executor-data)))) > "topology.enable.message.timeouts" does nothing > ----------------------------------------------- > > Key: STORM-549 > URL: https://issues.apache.org/jira/browse/STORM-549 > Project: Apache Storm > Issue Type: Bug > Affects Versions: 0.9.2-incubating, 0.9.1-incubating > Reporter: Sean T Allen > > The configuration option, added on 0.8.0 was never implemented: > ➜ apache-storm-0.9.2-incubating ag "topology.enable.message.timeouts" > conf/defaults.yaml > 122:topology.enable.message.timeouts: true > storm-core/src/jvm/backtype/storm/Config.java > 512: public static final String TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS = > "topology.enable.message.timeouts"; > ➜ apache-storm-0.9.2-incubating ag TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS > storm-core/src/jvm/backtype/storm/Config.java > 512: public static final String TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS = > "topology.enable.message.timeouts"; > 513: public static final Object TOPOLOGY_ENABLE_MESSAGE_TIMEOUTS_SCHEMA = > Boolean.class; -- This message was sent by Atlassian JIRA (v6.3.4#6332)