You need to include the zeromq Storm binding in your storm lib folder probably...it's no longer packaged together due to GPL licensing issues. I've never done this, but I think it was broken off into a separate github repository.
On Fri, Apr 4, 2014 at 7:01 AM, Daria Mayorova <[email protected]> wrote: > Thank you Susheel, > > We've tried to change this parameter, but the topology isn't initializing. > The following exception is returned: > > 2014-04-04 10:35:28 b.s.d.worker [ERROR] Error on initialization of server > mk-worker > java.lang.RuntimeException: Fail to construct messaging plugin from plugin > backtype.storm.messaging.zmq > at > backtype.storm.messaging.TransportFactory.makeContext(TransportFactory.java:53) > ~[storm-core-0.9.1-incubating.jar:0.9.1-incubating] > at > backtype.storm.daemon.worker$worker_data$fn__4263.invoke(worker.clj:185) > ~[na:0.9.1-incubating] > at backtype.storm.util$assoc_apply_self.invoke(util.clj:792) > ~[storm-core-0.9.1-incubating.jar:0.9.1-incubating] > at backtype.storm.daemon.worker$worker_data.invoke(worker.clj:181) > ~[storm-core-0.9.1-incubating.jar:0.9.1-incubating] > at > backtype.storm.daemon.worker$eval4413$exec_fn__1102__auto____4414.invoke(worker.clj:353) > ~[na:0.9.1-incubating] > at clojure.lang.AFn.applyToHelper(AFn.java:185) > [clojure-1.4.0.jar:na] > at clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.4.0.jar:na] > at clojure.core$apply.invoke(core.clj:601) ~[clojure-1.4.0.jar:na] > at > backtype.storm.daemon.worker$eval4413$mk_worker__4469.doInvoke(worker.clj:344) > [na:0.9.1-incubating] > at clojure.lang.RestFn.invoke(RestFn.java:512) > [clojure-1.4.0.jar:na] > at backtype.storm.daemon.worker$_main.invoke(worker.clj:454) > [na:0.9.1-incubating] > at clojure.lang.AFn.applyToHelper(AFn.java:172) > [clojure-1.4.0.jar:na] > at clojure.lang.AFn.applyTo(AFn.java:151) [clojure-1.4.0.jar:na] > at backtype.storm.daemon.worker.main(Unknown Source) > [storm-core-0.9.1-incubating.jar:0.9.1-incubating] > Caused by: java.lang.ClassNotFoundException: backtype.storm.messaging.zmq > at java.net.URLClassLoader$1.run(URLClassLoader.java:217) > ~[na:1.6.0_27] > at java.security.AccessController.doPrivileged(Native Method) > ~[na:1.6.0_27] > at java.net.URLClassLoader.findClass(URLClassLoader.java:205) > ~[na:1.6.0_27] > at java.lang.ClassLoader.loadClass(ClassLoader.java:321) > ~[na:1.6.0_27] > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) > ~[na:1.6.0_27] > at java.lang.ClassLoader.loadClass(ClassLoader.java:266) > ~[na:1.6.0_27] > at java.lang.Class.forName0(Native Method) ~[na:1.6.0_27] > at java.lang.Class.forName(Class.java:188) ~[na:1.6.0_27] > at > backtype.storm.messaging.TransportFactory.makeContext(TransportFactory.java:38) > ~[storm-core-0.9.1-incubating.jar:0.9.1-incubating] > ... 13 common frames omitted > 2014-04-04 10:35:28 b.s.util [INFO] Halting process: ("Error on > initialization") > > 0mq and jzmq are installed correctly on the machine, as before Storm 0.8.1 > was running on it using 0mq. > > Any other thing that should be done to make this work? > > > On Fri, Apr 4, 2014 at 10:52 AM, Susheel Kumar Gadalay < > [email protected]> wrote: > >> Set this parameter in storm.yaml >> >> storm.messaging.transport: "backtype.storm.messaging.zmq" >> >> On 4/4/14, Daria Mayorova <[email protected]> wrote: >> > Hi everyone, >> > >> > I am wondering whether it is possible to go back to using 0mq as >> transport >> > instead of Netty? I am pretty sure I saw some messages about switching >> back >> > to 0mq in Storm 0.9.1 at the old storm-user google group. >> > There is an issue related to this on Jira - >> > https://issues.apache.org/jira/browse/STORM-215 - but it seems to be >> > abandoned. >> > >> > Can anybody give me an idea of how this can be achieved? >> > >> > Thanks. >> > >> > Best regards, >> > Daria >> > >> > >
