[
https://issues.apache.org/jira/browse/STORM-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133686#comment-15133686
]
ASF GitHub Bot commented on STORM-1520:
---------------------------------------
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1077#discussion_r51978814
--- Diff:
storm-core/src/clj/org/apache/storm/cluster_state/zookeeper_state_factory.clj
---
@@ -144,7 +145,7 @@
(let [curator-listener (reify ConnectionStateListener
(stateChanged
[this client newState]
- (.stateChanged listener client
newState)))]
+ (.stateChanged listener
(StormConnectionStateConverter/convert newState))))]
--- End diff --
Thanks for kind words. :) I hope that Storm will get rid of many kinds of
type / signature / typo problems when ported to Java, static typed language.
> Nimbus Clojure/Zookeeper issue ("stateChanged" method not found)
> ----------------------------------------------------------------
>
> Key: STORM-1520
> URL: https://issues.apache.org/jira/browse/STORM-1520
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 1.0.0
> Reporter: P. Taylor Goetz
> Assignee: Jungtaek Lim
> Priority: Blocker
>
> Placeholder until I can gather more information for reproducing the issue.
> The following appears in nimbus.log after deploying/undeploying topologies:
> {code}
> 2016-02-02 21:34:04.308 o.a.s.s.o.a.c.f.l.ListenerContainer [ERROR] Listener
> (org.apache.storm.cluster_state.zookeeper_state_factory$_mkState$reify$reify__12660@22587507)
> threw an exception
> java.lang.IllegalArgumentException: No matching method found: stateChanged
> for class org.apache.storm.cluster$mk_storm_cluster_state$reify$reify__6413
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:53)
> at clojure.lang.Reflector.invokeInstanceMethod(Reflector.java:28)
> at
> org.apache.storm.cluster_state.zookeeper_state_factory$_mkState$reify$reify__12660.stateChanged(zookeeper_state_factory.clj:145)
> at
> org.apache.storm.shade.org.apache.curator.framework.state.ConnectionStateManager$2.apply(ConnectionStateManager.java:259)
> at
> org.apache.storm.shade.org.apache.curator.framework.state.ConnectionStateManager$2.apply(ConnectionStateManager.java:255)
> at
> org.apache.storm.shade.org.apache.curator.framework.listen.ListenerContainer$1.run(ListenerContainer.java:92)
> at
> org.apache.storm.shade.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:297)
> at
> org.apache.storm.shade.org.apache.curator.framework.listen.ListenerContainer.forEach(ListenerContainer.java:84)
> at
> org.apache.storm.shade.org.apache.curator.framework.state.ConnectionStateManager.processEvents(ConnectionStateManager.java:253)
> at
> org.apache.storm.shade.org.apache.curator.framework.state.ConnectionStateManager.access$000(ConnectionStateManager.java:43)
> at
> org.apache.storm.shade.org.apache.curator.framework.state.ConnectionStateManager$1.call(ConnectionStateManager.java:111)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> -Basic functionality does not seem to be affected.-
> Nimbus becomes unresponsive and needs to be manually restarted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
