Oh wow I forgot about the multi-JDK setup. I'm too much of a Windows noob to figure that out at the moment. I typically install a JDK into Windows Server using Chocolatey (package manager) because it's pretty hard to download and install applications without a bunch of server config first that I don't care about for testing. Also, since I haven't been able to build all the modules yet using Java 9 or higher exclusively (last I remember, there was an issue with the jmx gui module since it needs to link to the jmx module now instead of rt.jar or whatever), I can't test it with a simpler setup at the moment.
I still need to test this out in my normal environments, though. On Tue, 25 Jun 2019 at 09:51, Ralph Goers <[email protected]> wrote: > > Can you run just that test to see if you get stack traces? > > Ralph > > > On Jun 25, 2019, at 6:59 AM, Gary Gregory <[email protected]> wrote: > > > > Oops, hit send too soon. I get the test failures: > > > > ... > > [ERROR] Failures: > > [ERROR] ResolverUtilTest.testExtractPathFromFileUrl > > target\testpluginsutil failed with java.nio.file.FileSystemException: > > target\testpluginsutil\resolverutil2\customplugin2.jar: The process cannot > > access the file because it is being used by another process. > > > > [ERROR] ResolverUtilTest.testExtractPathFromFileUrlNotDecodedIfFileExists > > target\testpluginsutil failed with java.nio.file.FileSystemException: > > target\testpluginsutil\resolverutil2\customplugin2.jar: The process cannot > > access the file because it is being used by another process. > > > > [ERROR] ResolverUtilTest.testFileFromUriWithSpacesAndPlusCharactersInName > > target\testpluginsutil failed with java.nio.file.FileSystemException: > > target\testpluginsutil\resolverutil2\customplugin2.jar: The process cannot > > access the file because it is being used by another process. > > > > [ERROR] ResolverUtilTest.testFindInPackageFromJarPath > > target\testpluginsutil failed with java.nio.file.FileSystemException: > > target\testpluginsutil\resolverutil2\customplugin2.jar: The process cannot > > access the file because it is being used by another process. > > > > [INFO] > > [ERROR] Tests run: 2056, Failures: 4, Errors: 0, Skipped: 26 > > [INFO] > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Reactor Summary for Apache Log4j 2 2.12.0: > > [INFO] > > [INFO] Apache Log4j 2 ..................................... SUCCESS [ > > 6.669 s] > > [INFO] Apache Log4j API Java 9 support .................... SUCCESS [ > > 5.495 s] > > [INFO] Apache Log4j API ................................... SUCCESS [01:09 > > min] > > [INFO] Apache Log4j Implementation Java 9 support ......... SUCCESS [ > > 2.235 s] > > [INFO] Apache Log4j Core .................................. FAILURE [16:23 > > min] > > [INFO] Apache Log4j Core Integration Tests ................ SKIPPED > > ... > > > > using: > > > > Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; > > 2019-04-04T15:00:29-04:00) > > Maven home: C:\Java\apache-maven-3.6.1\bin\.. > > Java version: 1.8.0_212, vendor: Oracle Corporation, runtime: C:\Program > > Files\Java\jdk1.8.0_212\jre > > Default locale: en_US, platform encoding: Cp1252 > > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" > > > > Gary > > > > > > On Tue, Jun 25, 2019 at 9:58 AM Gary Gregory <[email protected]> wrote: > > > >> I get the following test failures: > >> > >> > >> On Sun, Jun 23, 2019 at 9:43 PM Ralph Goers <[email protected]> > >> wrote: > >> > >>> This is a vote to release Log4j 2.12.0, the next version of the Log4j 2 > >>> project. > >>> > >>> Please download, test, and cast your votes on the log4j developers list. > >>> [] +1, release the artifacts > >>> [] -1, don't release because... > >>> > >>> The vote will remain open for 72 hours (or more if required). All votes > >>> are welcome and we encourage everyone to test the release, but only > >>> Logging > >>> PMC votes are “officially” counted. As always, at least 3 +1 votes and > >>> more > >>> positive than negative votes are required. > >>> > >>> Changes in this release include: > >>> > >>> New Features > >>> > >>> • LOG4J2-2403: Allow zero padding the counter of a > >>> RollingFileAppender. Thanks to hupfdule. > >>> • LOG4J2-2427: Add filter that will match events when no marker > >>> is present. Thanks to Rimaljit Kaur. > >>> • LOG4J2-2406: Add reconfiguration methods to Configurator. > >>> • LOG4J2-913: Add support for reconfiguration via HTTP(S), > >>> Docker, and Spring Cloud Configuration. > >>> • LOG4J2-2586: TCP Appender should support a host name resolving > >>> to multiple IP addresses. > >>> • LOG4J2-2337: Allow custom end-of-line with JsonLayout. Thanks > >>> to Arvind Sahare, Patrice Ferrot. > >>> • LOG4J2-2598: GZIP compression on rollover supports configurable > >>> compression levels. Thanks to Carter Kozak. > >>> • LOG4J2-2611: AsyncQueueFullPolicy configuration short values > >>> "Default" and "Discard" are case insensitive to avoid confusion. > >>> • LOG4J2-2634: Add and use method > >>> org.apache.logging.log4j.message.MapMessage.toKey(String) for simpler > >>> subclasses. > >>> Fixed Bugs > >>> > >>> • LOG4J2-2547: RollingRandomAccessFileAppender error message > >>> referenced incorrect class name. > >>> • LOG4J2-2616: Restore constructor to ThrowablePatternConverter > >>> that was removed in 2.8.2. > >>> • LOG4J2-2622: StructuredDataId was ignoring maxLength atribute. > >>> • LOG4J2-2636: RFC5424Layout was not properly setting default > >>> Structured Element id for the MDC > >>> • LOG4J2-1143: Lookups were not found if the plugin key was not > >>> lowercase. Thanks to Pascal Heinrich. > >>> • LOG4J2-1852: Locate plugins within a Jar using a URL > >>> Connection. Thanks to Tanner Altares. > >>> • LOG4J2-2610: Explicitly set file creation time. > >>> • LOG4J2-2561: JEP223 version detection fix for JDK 9 and up. > >>> Thanks to Ulrich Enslin. > >>> • LOG4J2-1103: FailoverAppender was failing with ERROR appender > >>> Failover has no parameter that matches element Failovers. Thanks to Seán > >>> Dunne. > >>> • LOG4J2-2602: Update file time when size based triggering policy > >>> is used without a time-based triggering policy. > >>> • LOG4J2-2597: Throw better exception message when both > >>> log4j-slf4j-impl and log4j-to-slf4j are present. > >>> • LOG4J2-2559: NullPointerException in > >>> JdbcAppender.createAppender(). Thanks to Li Lei, Gary Gregory. > >>> • LOG4J2-2592: StackOverflowException when server not reachable > >>> with SocketAppender. Thanks to Dávid Kaya, Gary Gregory. > >>> • LOG4J2-2598: java.lang.StackOverflowError at > >>> org.apache.logging.log4j.junit.AbstractExternalFileCleaner.println(AbstractExternalFileCleaner.java:169). > >>> Thanks to Gary Gregory. > >>> • LOG4J2-2564: MapPatternConverter is properly created from the > >>> '%K', '%map', and '%MAP' patterns. PatternConverter instanceOf methods > >>> with > >>> unknown parameter types no longer elide those with known parameters. > >>> • LOG4J2-2612: NullPointerException at > >>> org.apache.logging.log4j.core.appender.db.jdbc.JdbcDatabaseManager.writeInternal(JdbcDatabaseManager.java:803). > >>> • LOG4J2-2618: Possible ClassCastException in > >>> org.apache.logging.log4j.core.script.ScriptManager.ScriptManager(Configuration, > >>> WatchManager) > >>> • LOG4J2-2631: RoutingAppender PurgePolicy implementations no > >>> longer stop appenders referenced from the logger configuration, only those > >>> that have been created by the RoutingAppender. Note that > >>> RoutingAppender.getAppenders no longer includes entries for referenced > >>> appenders, only those which it has created. > >>> • LOG4J2-2629: Fix a race allowing events not to be recorded when > >>> a RoutingAppender purge policy attempts to delete an idle appender at > >>> exactly the same time as a new event is recorded. > >>> • LOG4J2-2606: Asynchronous logging when the queue is full no > >>> longer results in heavy CPU utilization and low throughput. > >>> Changes > >>> > >>> • : Update tests from H2 1.4.197 to 1.4.199. Thanks to Gary > >>> Gregory. > >>> • LOG4J2-2570: Update Jackson from 2.9.7 to 2.9.8. Thanks to Gary > >>> Gregory. > >>> • LOG4J2-2574: Update MongoDB 3 module driver from 3.9.0 to > >>> 3.10.1. Thanks to Gary Gregory. > >>> • LOG4J2-2619: Update Jackson from 2.9.8 to 2.9.9. > >>> • LOG4J2-2634: Refactor several AsyncLogger methods below the 35 > >>> byte threshold for inlining. > >>> > >>> Tag: > >>> a) for a new copy do "git clone > >>> https://github.com/apache/logging-log4j2.git"; and then "git checkout > >>> tags/log4j-2.12.0-rc1” > >>> b) for an existing working copy to “git pull” and then “git checkout > >>> tags/log4j-2.12.0-rc1” > >>> > >>> Web Site: http://rgoers.github.io/log4j2-site/index.html. > >>> > >>> Maven Artifacts: > >>> https://repository.apache.org/content/repositories/orgapachelogging-1046 > >>> > >>> Distribution archives: > >>> https://dist.apache.org/repos/dist/dev/logging/log4j/ > >>> > >>> You may download all the Maven artifacts by executing: > >>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate > >>> https://repository.apache.org/content/repositories/orgapachelogging-1046/org/apache/logging/log4j/ > >>> > >>> Ralph > >>> > >> > > -- Matt Sicker <[email protected]>
