You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Stephen Armstrong <st...@linqia.com> on 2014/05/29 23:40:14 UTC

Fwd: LocalCluster throwing ClassNotFoundException

Hello,

I've been hitting the following ClassNotFoundException when running in
local mode:

java.lang.ClassNotFoundException:
backtype.storm.daemon.nimbus$normalize_conf$get_merged_conf_val__3916$fn__3917

Based on the thread:

https://groups.google.com/forum/#!searchin/storm-user/classnotfoundexception/storm-user/yOtE3Em50bA/tRP9CpMUNP0J

I tried setting the following log level in logback:

<logger name="backtype.storm.daemon.nimbus" level="INFO" />

which fixed it. While I'm now able to continue development, I'm curious if
anyone has any idea why this happens.

Also, if I don't use the logging level fix, I only get this error when I
have more than 3 components. Running a topology with 1 spout and 2 bolts
works fine, but adding a third causes this error to surface. Is there
something in Storm that only triggers when a topology is "sufficiently
complex" and that relies on logger.isInfoEnabled() or something?

Thanks
Steve

Re: LocalCluster throwing ClassNotFoundException

Posted by Stephen Armstrong <st...@linqia.com>.
I had thrown this onto Stack Overflow before a coworker suggested this
mailing list, so if anyone has any advice but prefers to answer there:
http://stackoverflow.com/questions/23923323/classnotfoundexception-when-trying-to-start-topology


On Thu, May 29, 2014 at 2:40 PM, Stephen Armstrong <
stephen.armstrong@linqia.com> wrote:

>
> Hello,
>
> I've been hitting the following ClassNotFoundException when running in
> local mode:
>
> java.lang.ClassNotFoundException:
> backtype.storm.daemon.nimbus$normalize_conf$get_merged_conf_val__3916$fn__3917
>
> Based on the thread:
>
>
> https://groups.google.com/forum/#!searchin/storm-user/classnotfoundexception/storm-user/yOtE3Em50bA/tRP9CpMUNP0J
>
> I tried setting the following log level in logback:
>
> <logger name="backtype.storm.daemon.nimbus" level="INFO" />
>
> which fixed it. While I'm now able to continue development, I'm curious if
> anyone has any idea why this happens.
>
> Also, if I don't use the logging level fix, I only get this error when I
> have more than 3 components. Running a topology with 1 spout and 2 bolts
> works fine, but adding a third causes this error to surface. Is there
> something in Storm that only triggers when a topology is "sufficiently
> complex" and that relies on logger.isInfoEnabled() or something?
>
> Thanks
> Steve
>
>
>