You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2011/01/25 03:03:44 UTC

[jira] Created: (HAMA-350) Add task log appender and Fix log4j rootLogger

Add task log appender and Fix log4j rootLogger
----------------------------------------------

                 Key: HAMA-350
                 URL: https://issues.apache.org/jira/browse/HAMA-350
             Project: Hama
          Issue Type: Bug
          Components: bsp
    Affects Versions: 0.2.0
            Reporter: Edward J. Yoon
            Assignee: Edward J. Yoon
             Fix For: 0.2.0


I've seen that all my logs comes with the message:

{code}
2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not find value for key log4j.appender.DEBUG
2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not instantiate appender named "DEBUG".
{code}

We need to fix rootLogger and, add task log appender.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HAMA-350) Add task log appender and Fix log4j rootLogger

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HAMA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986187#action_12986187 ] 

Hudson commented on HAMA-350:
-----------------------------

-1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12469231/HAMA-350.patch
against trunk revision 1063094.

    @author +1.  The patch does not contain any @author tags.

    tests included -1.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    javadoc +1.  The javadoc tool did not generate any warning messages.

    javac +1.  The applied patch does not generate any new javac compiler warnings.

    release audit +1.  The applied patch does not generate any new release audit warnings.

    findbugs -1.  The patch appears to introduce 1 new Findbugs warnings.

    core tests +1.  The patch passed core unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hama-Patch/307/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hama-Patch/307/findbugsResult/
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hama-Patch/307/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hama-Patch/307/console

This message is automatically generated.

> Add task log appender and Fix log4j rootLogger
> ----------------------------------------------
>
>                 Key: HAMA-350
>                 URL: https://issues.apache.org/jira/browse/HAMA-350
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 0.2.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.2.0
>
>         Attachments: HAMA-350.patch
>
>
> I've seen that all my logs comes with the message:
> {code}
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not find value for key log4j.appender.DEBUG
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not instantiate appender named "DEBUG".
> {code}
> We need to fix rootLogger and, add task log appender.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HAMA-350) Add task log appender and Fix log4j rootLogger

Posted by "Edward J. Yoon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward J. Yoon updated HAMA-350:
--------------------------------

    Attachment: HAMA-350.patch

This patch fixes above problems.

> Add task log appender and Fix log4j rootLogger
> ----------------------------------------------
>
>                 Key: HAMA-350
>                 URL: https://issues.apache.org/jira/browse/HAMA-350
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 0.2.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.2.0
>
>         Attachments: HAMA-350.patch
>
>
> I've seen that all my logs comes with the message:
> {code}
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not find value for key log4j.appender.DEBUG
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not instantiate appender named "DEBUG".
> {code}
> We need to fix rootLogger and, add task log appender.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HAMA-350) Add task log appender and Fix log4j rootLogger

Posted by "Edward J. Yoon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward J. Yoon updated HAMA-350:
--------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

This issue is fixed.

> Add task log appender and Fix log4j rootLogger
> ----------------------------------------------
>
>                 Key: HAMA-350
>                 URL: https://issues.apache.org/jira/browse/HAMA-350
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 0.2.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.2.0
>
>         Attachments: HAMA-350.patch
>
>
> I've seen that all my logs comes with the message:
> {code}
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not find value for key log4j.appender.DEBUG
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not instantiate appender named "DEBUG".
> {code}
> We need to fix rootLogger and, add task log appender.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HAMA-350) Add task log appender and Fix log4j rootLogger

Posted by "Edward J. Yoon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HAMA-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward J. Yoon updated HAMA-350:
--------------------------------

    Status: Patch Available  (was: Open)

running patch through hudson.

> Add task log appender and Fix log4j rootLogger
> ----------------------------------------------
>
>                 Key: HAMA-350
>                 URL: https://issues.apache.org/jira/browse/HAMA-350
>             Project: Hama
>          Issue Type: Bug
>          Components: bsp
>    Affects Versions: 0.2.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.2.0
>
>         Attachments: HAMA-350.patch
>
>
> I've seen that all my logs comes with the message:
> {code}
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not find value for key log4j.appender.DEBUG
> 2011-01-25 10:41:57,479 INFO org.apache.hama.bsp.TaskRunner: attempt_201101251040_0002_m_000001_0 log4j:ERROR Could not instantiate appender named "DEBUG".
> {code}
> We need to fix rootLogger and, add task log appender.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.