FAQ
Hi All,

I'm a Storm newbie so please be kind ;) I'm using Storm 0.8.2 with Java
1.7.0_07 and python 2.6 on a Suse 11 SP2 box.

We would like to log all worker activities onto a JMS queue (ActiveMQ) for
further processing and analysis at some time.
Our worker is setup with the following log4j.xml (see attachment)

If we remove the comment on line 32 then starting storm will freeze with
the following message:

log4j:WARN No appenders could be found for logger
(org.apache.activemq.transport.WireFormatNegotiator).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.

I tried passing options such as
worker.childopts="-Dlog4j.configuration=config/log4j.xml" but it is not
working... in fact, I found this option in another thread but the storm
Python script has no mention of it anywhere.

When I strace the process (master and children) I can see that it is jammed
in the conf_value function of the Python script (around line 61) which
opens a PIPE between two processes.
Could it be that the warning is causing this to hang?

How can I fix this?

Thanks

Search Discussions

  • Poisson125 at Dec 8, 2013 at 3:33 pm
    Hello.

    Try to use storm 0.9.0, it uses logback instead of log4j. It happens mostly
    because of conflicts between the logging libs in ActiveMQ jar and log4j.



    Le vendredi 21 décembre 2012 16:33:19 UTC-5, jsvachon a écrit :
    Hi All,

    I'm a Storm newbie so please be kind ;) I'm using Storm 0.8.2 with Java
    1.7.0_07 and python 2.6 on a Suse 11 SP2 box.

    We would like to log all worker activities onto a JMS queue (ActiveMQ) for
    further processing and analysis at some time.
    Our worker is setup with the following log4j.xml (see attachment)

    If we remove the comment on line 32 then starting storm will freeze with
    the following message:

    log4j:WARN No appenders could be found for logger
    (org.apache.activemq.transport.WireFormatNegotiator).
    log4j:WARN Please initialize the log4j system properly.
    log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
    more info.

    I tried passing options such as
    worker.childopts="-Dlog4j.configuration=config/log4j.xml" but it is not
    working... in fact, I found this option in another thread but the storm
    Python script has no mention of it anywhere.

    When I strace the process (master and children) I can see that it is
    jammed in the conf_value function of the Python script (around line 61)
    which opens a PIPE between two processes.
    Could it be that the warning is causing this to hang?

    How can I fix this?

    Thanks
    --
    You received this message because you are subscribed to the Google Groups "storm-user" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to storm-user+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupstorm-user @
postedDec 25, '12 at 6:49a
activeDec 8, '13 at 3:33p
posts2
users2
websitestorm-project.net
irc#storm-user

2 users in discussion

Poisson125: 1 post Jsvachon: 1 post

People

Translate

site design / logo © 2022 Grokbase