logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ludovic HOCHET (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (LOG4J2-1850) Cassendra's integration test fails on Windows
Date Sun, 12 Mar 2017 23:05:04 GMT

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

Ludovic HOCHET updated LOG4J2-1850:
-----------------------------------
    Comment: was deleted

(was: After investigating, this is due to the CassandraDaemon (in the CassendraRule) calling
System.exit(..) when on Windows.
The attached patch-log4j2-1850.diff prevents System.exit(..) from completing by installing
a temporary security manager that denies the vmExit permission. The previous security manager
is restored after the call to daemon.stop().)

> Cassendra's integration test fails on Windows
> ---------------------------------------------
>
>                 Key: LOG4J2-1850
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1850
>             Project: Log4j 2
>          Issue Type: Bug
>    Affects Versions: 2.8.2
>         Environment: Windows 10
>            Reporter: Ludovic HOCHET
>            Priority: Minor
>         Attachments: patch-log4j2-1850.diff
>
>
> 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:
> {quote}
> --- 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
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message