You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/10/30 19:08:33 UTC

[jira] [Updated] (SAMZA-450) Unable to override log4j.xml with task.opts

     [ https://issues.apache.org/jira/browse/SAMZA-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini updated SAMZA-450:
----------------------------------
    Attachment: SAMZA-450-1.patch
                SAMZA-450-0.patch

RB for 0.8.0 branch (SAMZA-450-0.patch):

https://reviews.apache.org/r/27388

RB for master branch (SAMZA-450-1.patch):

https://reviews.apache.org/r/27389

Changes made:

# Eliminate SAMZA_LOG4J_CONFIG environment variable.
# Check All four system properties (listed in JIRA description) to see if they're set in JAVA_OPTS, and only set them if they're not already set.
# Fix log line in ThreadJobFactory.

Ran 0.8.0 test locally and verified that run-job.sh uses log4j-console.xml, while the ProcessJob receives log4j.xml.

> Unable to override log4j.xml with task.opts
> -------------------------------------------
>
>                 Key: SAMZA-450
>                 URL: https://issues.apache.org/jira/browse/SAMZA-450
>             Project: Samza
>          Issue Type: Bug
>          Components: container
>    Affects Versions: 0.8.0, 0.9.0
>            Reporter: Chris Riccomini
>            Assignee: Chris Riccomini
>             Fix For: 0.8.0, 0.9.0
>
>         Attachments: SAMZA-450-0.patch, SAMZA-450-1.patch
>
>
> If you specify a log4j.configuration via task.opts, this setting is ignored. This problem extends to all of the following properties:
> {noformat}
> log4j.configuration
> samza.log.dir
> samza.container.name
> java.io.tmpdir
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)