Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-1850

Cassendra's integration test fails on Windows

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.8.2
    • Fix Version/s: 2.8.2
    • Component/s: None
    • Labels:
      None
    • Environment:

      Windows 10

      Description

      While verifying LOG4J2-1753 I tried to clean build the whole Log4J project, it failed during the integration tests of the log4j-nosql module with the following:

      — maven-failsafe-plugin:2.19.1:integration-test (integration-tests) @ log4j-nosql —
      file.encoding cannot be set as system property, use <argLine>-Dfile.encoding=...</argLine> instead

      -------------------------------------------------------
      T E S T S
      -------------------------------------------------------
      Running org.apache.logging.log4j.nosql.appender.cassandra.CassandraAppenderIT
      ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.
      23:32:33.958 [Log4j2-TF-1-Cassandra-1] ERROR org.apache.cassandra.service.StartupChecks - cassandra.jmx.local.port missing from cassandra-env.sh, unable to start local JMX service.
      ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.

      Results :

      Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

      — maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql —
      ------------------------------------------------------------------------
      BUILD FAILURE
      ------------------------------------------------------------------------
      Total time: 29.346 s
      Finished at: 2017-03-12T23:32:49+01:00
      Final Memory: 30M/516M
      ------------------------------------------------------------------------
      Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (verify) on project log4j-nosql: There was a timeout or other error in the fork -> [Help 1]

      To see the full stack trace of the errors, re-run Maven with the -e switch.
      Re-run Maven using the -X switch to enable full debug logging.

      For more information about the errors and possible solutions, please read the following articles:
      [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

        Attachments

          Activity

            People

            • Assignee:
              jvz Matt Sicker
              Reporter:
              lhochet Ludovic HOCHET
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: