You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/07/05 21:53:16 UTC

[jira] [Created] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

initialize log4j correctly in EmbeddedCassandraService
------------------------------------------------------

                 Key: CASSANDRA-2857
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
             Project: Cassandra
          Issue Type: Bug
            Reporter: Jonathan Ellis
            Assignee: Jonathan Ellis
            Priority: Trivial
         Attachments: 2857.txt

Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2857:
--------------------------------------

    Attachment: 2857-drivers.txt
                2857.txt

> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.2
>
>         Attachments: 2857-drivers.txt, 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

Posted by "T Jake Luciani (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092890#comment-13092890 ] 

T Jake Luciani commented on CASSANDRA-2857:
-------------------------------------------

needs rebase but +1

> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.5
>
>         Attachments: 2857-drivers.txt, 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2857:
--------------------------------------

    Attachment:     (was: 2857.txt)

> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.2
>
>         Attachments: 2857-drivers.txt, 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

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

Hudson commented on CASSANDRA-2857:
-----------------------------------

Integrated in Cassandra-0.8 #298 (See [https://builds.apache.org/job/Cassandra-0.8/298/])
    fix log4j initialization in EmbeddedCassandraService
patch by jbellis; reviewed by tjake for CASSANDRA-2857

jbellis : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1162851
Files : 
* /cassandra/branches/cassandra-0.8/CHANGES.txt
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/AbstractCassandraDaemon.java
* /cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/thrift/CassandraDaemon.java


> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.5
>
>         Attachments: 2857-drivers.txt, 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2857:
--------------------------------------

    Attachment: 2857.txt

patch to move the log4j initialization into the "real" entry point classes

> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.2
>
>         Attachments: 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2857:
--------------------------------------

    Attachment:     (was: 2857.txt)

> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.2
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-2857) initialize log4j correctly in EmbeddedCassandraService

Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-2857:
--------------------------------------

    Attachment: 2857.txt

> initialize log4j correctly in EmbeddedCassandraService
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2857
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2857
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Trivial
>             Fix For: 0.8.2
>
>         Attachments: 2857-drivers.txt, 2857.txt
>
>
> Currently, ECS.cleanUpOldStuff calls CleanupHelper.cleanupAndLeaveDirs(), which initialized DatabaseDescriptor which does some logging.  When we go to initialize log4j later in AbstractCassandraService, it's too late.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira