Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-2611

static block in AbstractCassandraDaemon makes it difficult to change log4j behavoiur

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Low
    • Resolution: Not A Problem
    • None
    • None
    • Windows 7

    Description

      We embed Cassandra in our application - mainly because our webservices are such a thin layer on top of Cassandra that it really does not make sense for us to have Cassandra in an external JVM. In 0.7.0 this was all fine. Now upgrading to 0.7.5, there is a static block in AbstractCassandraDaemon. This gets called when the class is loaded causing us issues as we have not generated the log4j.properties file at this point in time.

      Can this not be a protected method that is called when AbstractCassandraDaemon is constructed? That way a) I can control the behaviour and b) my log4j.properties file will have been generated by then.

      Thanks.

      Attachments

        1. CASSANDRA-2611-test.patch
          2 kB
          Tommy Tynjä
        2. CASSANDRA-2611.patch
          0.5 kB
          Tommy Tynjä

        Activity

          People

            Unassigned Unassigned
            keteracel Paul Loy
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: