Re: SyslogAppender parameter name change

[Matt Sicker]

I see. There were a couple issues with @PluginAliases for SyslogAppender
specifically. Fixed in master.

On 3 February 2017 at 10:23, Matt Sicker  wrote:

> Plugins can have aliases via @PluginAliases (see for example <
> https://github.com/apache/logging-log4j2/blob/master/
> log4j-core/src/main/java/org/apache/logging/log4j/core/
> appender/mom/JmsAppender.java>), don't recall if attributes are
> supported. If not, that's a feature we can support for sure.
>
> On 2 February 2017 at 18:27, Gary Gregory  wrote:
>
>> Darn, I apologize for that one.
>>
>> Gary
>>
>> On Thu, Feb 2, 2017 at 4:09 PM, Remko Popma 
>> wrote:
>>
>>> Sorry for that and thanks for letting us know!
>>>
>>> I wonder if parameter names can have aliases so we can support both the
>>> old and the new name without causing users inconvenience. If possible we
>>> should address this for 2.8.1.
>>>
>>> Remko
>>>
>>> Sent from my iPhone
>>>
>>> On Feb 3, 2017, at 4:13, Sam Beroz  wrote:
>>>
>>> The reconnectionDelayMillis parameter was renamed
>>> to reconnectDelayMillis. After updating to release 2.8 I noticed that I was
>>> getting the following error:
>>>
>>> ERROR Syslog contains an invalid element or attribute
>>> "reconnectionDelayMillis"
>>>
>>>
>>> It appears that change was part of this commit:
>>>
>>> commit ed828be67a23ee3513cafc9d2fd0ff16a26c7013
>>> Author: Gary Gregory 
>>> Date:   Mon Nov 14 15:11:47 2016 -0800
>>>
>>> [LOG4J2-1709]
>>>
>>> Add a Builder to SyslogAppender and deprecate
>>> SyslogAppender.createAppender().
>>>
>>>
>>>
>>> The documentation (https://logging.apache.org/lo
>>> g4j/2.x/manual/appenders.html#SyslogAppender) still has the parameter
>>> listed as "reconnectionDelayMillis" but the code is now obviously
>>> looking for "reconnectDelayMillis". I'm going to change my config to
>>> use the new name, but I thought I'd point out the disconnect as it had me
>>> confused for a bit. Thanks - Sam
>>>
>>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> Java Persistence with Hibernate, Second Edition
>> 
>>
>> 
>> JUnit in Action, Second Edition
>> 
>>
>> 
>> Spring Batch in Action
>> 
>> 
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>>
>
>
>
> --
> Matt Sicker 
>



-- 
Matt Sicker 

Re: RollingAppenderSizeTest failures

[Gary Gregory]

I have customers that develop on Windows and then deploy to everything from
Windows Server boxes (more than you think), AIX, Linux, Linux on Z, you
name it.

G

On Fri, Feb 3, 2017 at 2:52 PM, Apache  wrote:

> Yeah - the idea of using Java on Windows seems like it would be an
> anti-pattern to me.
>
> Ralph
>
> On Feb 3, 2017, at 3:37 PM, Matt Sicker  wrote:
>
> I mean when it comes down to production use of Cassandra, I really doubt
> anyone is using it on Windows. Then again, I've never seen Windows Server
> used for big data clusters in the first place, so I suppose it's possible.
>
> On 3 February 2017 at 16:23, Gary Gregory  wrote:
>
>> I hope running Cassandra on Windows is not a problem. I seems like a
>> normal set up: https://www.datastax.com/2012/01/getting-started-with-ap
>> ache-cassandra-on-windows-the-easy-way
>>
>> G
>>
>> On Fri, Feb 3, 2017 at 12:10 PM, Matt Sicker  wrote:
>>
>>> That's strange. I never tested that integration test in Windows, so
>>> perhaps it's platform-specific? Anyways, the equivalent Mongo integration
>>> test is @Ignore'd due to requiring a running Mongo, and the Cassandra test
>>> works similarly although it starts up Cassandra within the JVM for you.
>>>
>>> On 3 February 2017 at 13:10, Gary Gregory 
>>> wrote:
>>>
 And if I ignore THAT OSGi test, I then fail in nosql :-(

 [INFO] --- maven-failsafe-plugin:2.19.1:integration-test
 (integration-tests) @ log4j-nosql ---

 ---
  T E S T S
 ---
 Running org.apache.logging.log4j.nosql.appender.cassandra.CassandraA
 ppenderIT
 ERROR StatusLogger No log4j2 configuration file found. Using default
 configuration: logging only errors to the console.
 11:00:39.333 [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.

 Results :

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

 [INFO]
 [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql
 ---
 [INFO] 
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] Apache Log4j NoSQL . FAILURE [
 27.242 s]
 [INFO] Apache Log4J Performance Tests . SKIPPED
 [INFO] Apache Log4j Streaming Interface ... SKIPPED
 [INFO] Apache Log4j JUL Adapter ... SKIPPED
 [INFO] Apache Log4j Liquibase Binding . SKIPPED
 [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 29.063 s
 [INFO] Finished at: 2017-02-03T11:00:55-08:00
 [INFO] Final Memory: 49M/691M
 [INFO] 
 
 [ERROR] 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]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1] http://cwiki.apache.org/conflu
 ence/display/MAVEN/MojoExecutionException

 Thoughts?

 Gary

 On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory 
 wrote:

> If I @Ignore that one test, then I get (mvn clean install):
>
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842
> sec - in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBu
> ndleTest
> at org.junit.internal.runners.sta
> tements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.sta
> tements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.rules.ExternalResour
> ce$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner
> .runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4C
> lassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4C
> lassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentR

Re: RollingAppenderSizeTest failures

[Apache]

Yeah - the idea of using Java on Windows seems like it would be an anti-pattern 
to me.

Ralph

> On Feb 3, 2017, at 3:37 PM, Matt Sicker  wrote:
> 
> I mean when it comes down to production use of Cassandra, I really doubt 
> anyone is using it on Windows. Then again, I've never seen Windows Server 
> used for big data clusters in the first place, so I suppose it's possible.
> 
> On 3 February 2017 at 16:23, Gary Gregory  > wrote:
> I hope running Cassandra on Windows is not a problem. I seems like a normal 
> set up: 
> https://www.datastax.com/2012/01/getting-started-with-apache-cassandra-on-windows-the-easy-way
>  
> 
> 
> G
> 
> On Fri, Feb 3, 2017 at 12:10 PM, Matt Sicker  > wrote:
> That's strange. I never tested that integration test in Windows, so perhaps 
> it's platform-specific? Anyways, the equivalent Mongo integration test is 
> @Ignore'd due to requiring a running Mongo, and the Cassandra test works 
> similarly although it starts up Cassandra within the JVM for you.
> 
> On 3 February 2017 at 13:10, Gary Gregory  > wrote:
> And if I ignore THAT OSGi test, I then fail in nosql :-(
> 
> [INFO] --- maven-failsafe-plugin:2.19.1:integration-test (integration-tests) 
> @ log4j-nosql ---
> 
> ---
>  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.
> 11:00:39.333 [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.
> 
> Results :
> 
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> 
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j NoSQL . FAILURE [ 27.242 
> s]
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29.063 s
> [INFO] Finished at: 2017-02-03T11:00:55-08:00
> [INFO] Final Memory: 49M/691M
> [INFO] 
> 
> [ERROR] 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]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 
> 
> 
> Thoughts?
> 
> Gary
> 
> On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory  > wrote:
> If I @Ignore that one test, then I get (mvn clean install):
> 
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842 sec - 
> in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBundleTest
> at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at 
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at

Re: RollingAppenderSizeTest failures

[Matt Sicker]

I mean when it comes down to production use of Cassandra, I really doubt
anyone is using it on Windows. Then again, I've never seen Windows Server
used for big data clusters in the first place, so I suppose it's possible.

On 3 February 2017 at 16:23, Gary Gregory  wrote:

> I hope running Cassandra on Windows is not a problem. I seems like a
> normal set up: https://www.datastax.com/2012/01/getting-started-with-
> apache-cassandra-on-windows-the-easy-way
>
> G
>
> On Fri, Feb 3, 2017 at 12:10 PM, Matt Sicker  wrote:
>
>> That's strange. I never tested that integration test in Windows, so
>> perhaps it's platform-specific? Anyways, the equivalent Mongo integration
>> test is @Ignore'd due to requiring a running Mongo, and the Cassandra test
>> works similarly although it starts up Cassandra within the JVM for you.
>>
>> On 3 February 2017 at 13:10, Gary Gregory  wrote:
>>
>>> And if I ignore THAT OSGi test, I then fail in nosql :-(
>>>
>>> [INFO] --- maven-failsafe-plugin:2.19.1:integration-test
>>> (integration-tests) @ log4j-nosql ---
>>>
>>> ---
>>>  T E S T S
>>> ---
>>> Running org.apache.logging.log4j.nosql.appender.cassandra.CassandraA
>>> ppenderIT
>>> ERROR StatusLogger No log4j2 configuration file found. Using default
>>> configuration: logging only errors to the console.
>>> 11:00:39.333 [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.
>>>
>>> Results :
>>>
>>> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>>
>>> [INFO]
>>> [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql
>>> ---
>>> [INFO] 
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Apache Log4j NoSQL . FAILURE [
>>> 27.242 s]
>>> [INFO] Apache Log4J Performance Tests . SKIPPED
>>> [INFO] Apache Log4j Streaming Interface ... SKIPPED
>>> [INFO] Apache Log4j JUL Adapter ... SKIPPED
>>> [INFO] Apache Log4j Liquibase Binding . SKIPPED
>>> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
>>> [INFO] 
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO] 
>>> 
>>> [INFO] Total time: 29.063 s
>>> [INFO] Finished at: 2017-02-03T11:00:55-08:00
>>> [INFO] Final Memory: 49M/691M
>>> [INFO] 
>>> 
>>> [ERROR] 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]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1] http://cwiki.apache.org/conflu
>>> ence/display/MAVEN/MojoExecutionException
>>>
>>> Thoughts?
>>>
>>> Gary
>>>
>>> On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory 
>>> wrote:
>>>
 If I @Ignore that one test, then I get (mvn clean install):

 Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842
 sec - in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBu
 ndleTest
 at org.junit.internal.runners.statements.InvokeMethod.evaluate(
 InvokeMethod.java:17)
 at org.junit.internal.runners.statements.RunBefores.evaluate(Ru
 nBefores.java:26)
 at org.junit.rules.ExternalResource$1.evaluate(ExternalResource
 .java:48)
 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325
 )
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
 4ClassRunner.java:78)
 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
 4ClassRunner.java:57)
 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:
 71)
 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java
 :288)
 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:
 58)
 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:
 268)
 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
 at org.apa

Re: RollingAppenderSizeTest failures

[Gary Gregory]

I hope running Cassandra on Windows is not a problem. I seems like a normal
set up:
https://www.datastax.com/2012/01/getting-started-with-apache-cassandra-on-windows-the-easy-way

G

On Fri, Feb 3, 2017 at 12:10 PM, Matt Sicker  wrote:

> That's strange. I never tested that integration test in Windows, so
> perhaps it's platform-specific? Anyways, the equivalent Mongo integration
> test is @Ignore'd due to requiring a running Mongo, and the Cassandra test
> works similarly although it starts up Cassandra within the JVM for you.
>
> On 3 February 2017 at 13:10, Gary Gregory  wrote:
>
>> And if I ignore THAT OSGi test, I then fail in nosql :-(
>>
>> [INFO] --- maven-failsafe-plugin:2.19.1:integration-test
>> (integration-tests) @ log4j-nosql ---
>>
>> ---
>>  T E S T S
>> ---
>> Running org.apache.logging.log4j.nosql.appender.cassandra.CassandraA
>> ppenderIT
>> ERROR StatusLogger No log4j2 configuration file found. Using default
>> configuration: logging only errors to the console.
>> 11:00:39.333 [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.
>>
>> Results :
>>
>> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>
>> [INFO]
>> [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
>> [INFO] 
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Log4j NoSQL . FAILURE [
>> 27.242 s]
>> [INFO] Apache Log4J Performance Tests . SKIPPED
>> [INFO] Apache Log4j Streaming Interface ... SKIPPED
>> [INFO] Apache Log4j JUL Adapter ... SKIPPED
>> [INFO] Apache Log4j Liquibase Binding . SKIPPED
>> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 29.063 s
>> [INFO] Finished at: 2017-02-03T11:00:55-08:00
>> [INFO] Final Memory: 49M/691M
>> [INFO] 
>> 
>> [ERROR] 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]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/conflu
>> ence/display/MAVEN/MojoExecutionException
>>
>> Thoughts?
>>
>> Gary
>>
>> On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory 
>> wrote:
>>
>>> If I @Ignore that one test, then I get (mvn clean install):
>>>
>>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842
>>> sec - in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBu
>>> ndleTest
>>> at org.junit.internal.runners.statements.InvokeMethod.evaluate(
>>> InvokeMethod.java:17)
>>> at org.junit.internal.runners.statements.RunBefores.evaluate(Ru
>>> nBefores.java:26)
>>> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource
>>> .java:48)
>>> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>>> 4ClassRunner.java:78)
>>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>>> 4ClassRunner.java:57)
>>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:
>>> 71)
>>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java
>>> :288)
>>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:
>>> 58)
>>> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:
>>> 268)
>>> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>>> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUni
>>> t4Provider.java:367)
>>> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithR
>>> erun(JUnit4Provider.java:274)
>>> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestS
>>> et(JUnit4Provider.java:238)
>>> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit
>>> 4Provider.java:161)
>>

JDK 9 EA Build 155 is available on java.net

[Rory O'Donnell]

Hi Nick,

*JDK 9 Early Access* b155   is 
available on java.net



There have been a number of fixes to bugs reported by Open Source 
projects since the last availability email  :


 * b155 - JDK-8167273 : Calendar.getDisplayNames inconsistent with
   DateFormatSymbols
 * b154 - JDK-8157611 : field visiblePackages is null for the unnamed
   module producing NPE when accessed
 * b153 - JDK-8163449 : Allow per protocol setting for URLConnection
   defaultUseCaches
 * b152 - JDK-8172158 : Annotation processor not run with -source <= 8


Dalibor and I are presenting at FOSDEM this weekend, we would love to 
meet you there!


 * JDK 9 Outreach - The Awesome Parts
   


Rgds,Rory

--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

Re: RollingAppenderSizeTest failures

[Matt Sicker]

If embedded Cassandra doesn't work in Windows, then a JUnit
Assume.assumeFalse(isWindows()) could be added to the beginning of the
test. We have an isWindows() method somewhere in log4j-core or -api.

On 3 February 2017 at 14:27, Apache  wrote:

> They almost always seem to be platform specific, and almost always
> something to do with Windows. On the last one I find it odd that it
> mentions cassandra-env.sh. Obviously a shell script won’t normally run on
> windows, but I think I looked at that error several days ago and it seemed
> like no shell script should be involved.
>
> Ralph
>
> On Feb 3, 2017, at 1:10 PM, Matt Sicker  wrote:
>
> That's strange. I never tested that integration test in Windows, so
> perhaps it's platform-specific? Anyways, the equivalent Mongo integration
> test is @Ignore'd due to requiring a running Mongo, and the Cassandra test
> works similarly although it starts up Cassandra within the JVM for you.
>
> On 3 February 2017 at 13:10, Gary Gregory  wrote:
>
>> And if I ignore THAT OSGi test, I then fail in nosql :-(
>>
>> [INFO] --- maven-failsafe-plugin:2.19.1:integration-test
>> (integration-tests) @ log4j-nosql ---
>>
>> ---
>>  T E S T S
>> ---
>> Running org.apache.logging.log4j.nosql.appender.cassandra.CassandraA
>> ppenderIT
>> ERROR StatusLogger No log4j2 configuration file found. Using default
>> configuration: logging only errors to the console.
>> 11:00:39.333 [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.
>>
>> Results :
>>
>> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>>
>> [INFO]
>> [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
>> [INFO] 
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Log4j NoSQL . FAILURE [
>> 27.242 s]
>> [INFO] Apache Log4J Performance Tests . SKIPPED
>> [INFO] Apache Log4j Streaming Interface ... SKIPPED
>> [INFO] Apache Log4j JUL Adapter ... SKIPPED
>> [INFO] Apache Log4j Liquibase Binding . SKIPPED
>> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 29.063 s
>> [INFO] Finished at: 2017-02-03T11:00:55-08:00
>> [INFO] Final Memory: 49M/691M
>> [INFO] 
>> 
>> [ERROR] 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]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/conflu
>> ence/display/MAVEN/MojoExecutionException
>>
>> Thoughts?
>>
>> Gary
>>
>> On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory 
>> wrote:
>>
>>> If I @Ignore that one test, then I get (mvn clean install):
>>>
>>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842
>>> sec - in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBu
>>> ndleTest
>>> at org.junit.internal.runners.statements.InvokeMethod.evaluate(
>>> InvokeMethod.java:17)
>>> at org.junit.internal.runners.statements.RunBefores.evaluate(Ru
>>> nBefores.java:26)
>>> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource
>>> .java:48)
>>> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>>> 4ClassRunner.java:78)
>>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>>> 4ClassRunner.java:57)
>>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:
>>> 71)
>>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java
>>> :288)
>>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:
>>> 58)
>>> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:
>>> 268)
>>> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>>> a

Re: RollingAppenderSizeTest failures

[Apache]

They almost always seem to be platform specific, and almost always something to 
do with Windows. On the last one I find it odd that it mentions 
cassandra-env.sh. Obviously a shell script won’t normally run on windows, but I 
think I looked at that error several days ago and it seemed like no shell 
script should be involved.

Ralph

> On Feb 3, 2017, at 1:10 PM, Matt Sicker  wrote:
> 
> That's strange. I never tested that integration test in Windows, so perhaps 
> it's platform-specific? Anyways, the equivalent Mongo integration test is 
> @Ignore'd due to requiring a running Mongo, and the Cassandra test works 
> similarly although it starts up Cassandra within the JVM for you.
> 
> On 3 February 2017 at 13:10, Gary Gregory  > wrote:
> And if I ignore THAT OSGi test, I then fail in nosql :-(
> 
> [INFO] --- maven-failsafe-plugin:2.19.1:integration-test (integration-tests) 
> @ log4j-nosql ---
> 
> ---
>  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.
> 11:00:39.333 [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.
> 
> Results :
> 
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> 
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j NoSQL . FAILURE [ 27.242 
> s]
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29.063 s
> [INFO] Finished at: 2017-02-03T11:00:55-08:00
> [INFO] Final Memory: 49M/691M
> [INFO] 
> 
> [ERROR] 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]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 
> 
> 
> Thoughts?
> 
> Gary
> 
> On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory  > wrote:
> If I @Ignore that one test, then I get (mvn clean install):
> 
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842 sec - 
> in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBundleTest
> at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at 
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at 
> org.apache.maven.surefire.

Re: RollingAppenderSizeTest failures

[Matt Sicker]

That's strange. I never tested that integration test in Windows, so perhaps
it's platform-specific? Anyways, the equivalent Mongo integration test is
@Ignore'd due to requiring a running Mongo, and the Cassandra test works
similarly although it starts up Cassandra within the JVM for you.

On 3 February 2017 at 13:10, Gary Gregory  wrote:

> And if I ignore THAT OSGi test, I then fail in nosql :-(
>
> [INFO] --- maven-failsafe-plugin:2.19.1:integration-test
> (integration-tests) @ log4j-nosql ---
>
> ---
>  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.
> 11:00:39.333 [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.
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j NoSQL . FAILURE [
> 27.242 s]
> [INFO] Apache Log4J Performance Tests . SKIPPED
> [INFO] Apache Log4j Streaming Interface ... SKIPPED
> [INFO] Apache Log4j JUL Adapter ... SKIPPED
> [INFO] Apache Log4j Liquibase Binding . SKIPPED
> [INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29.063 s
> [INFO] Finished at: 2017-02-03T11:00:55-08:00
> [INFO] Final Memory: 49M/691M
> [INFO] 
> 
> [ERROR] 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]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoExecutionException
>
> Thoughts?
>
> Gary
>
> On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory 
> wrote:
>
>> If I @Ignore that one test, then I get (mvn clean install):
>>
>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842 sec
>> - in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBundleTest
>> at org.junit.internal.runners.statements.InvokeMethod.evaluate(
>> InvokeMethod.java:17)
>> at org.junit.internal.runners.statements.RunBefores.evaluate(
>> RunBefores.java:26)
>> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource
>> .java:48)
>> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>> 4ClassRunner.java:78)
>> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit
>> 4ClassRunner.java:57)
>> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:
>> 71)
>> at org.junit.runners.ParentRunner.runChildren(ParentRunner.
>> java:288)
>> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:
>> 58)
>> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:
>> 268)
>> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUni
>> t4Provider.java:367)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithR
>> erun(JUnit4Provider.java:274)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestS
>> et(JUnit4Provider.java:238)
>> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit
>> 4Provider.java:161)
>> at org.apache.maven.surefire.booter.ForkedBooter.invokeProvider
>> InSameClassLoader(ForkedBooter.java:290)
>> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInPro
>> cess(ForkedBooter.java:242)
>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBoo
>> ter.java:121)
>> Caused by: java.lang.ClassNotFoundE

Re: RollingAppenderSizeTest failures

[Gary Gregory]

And if I ignore THAT OSGi test, I then fail in nosql :-(

[INFO] --- maven-failsafe-plugin:2.19.1:integration-test
(integration-tests) @ log4j-nosql ---

---
 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.
11:00:39.333 [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.

Results :

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

[INFO]
[INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ log4j-nosql ---
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j NoSQL . FAILURE [
27.242 s]
[INFO] Apache Log4J Performance Tests . SKIPPED
[INFO] Apache Log4j Streaming Interface ... SKIPPED
[INFO] Apache Log4j JUL Adapter ... SKIPPED
[INFO] Apache Log4j Liquibase Binding . SKIPPED
[INFO] Apache Log4j Scala 2.10 wrapper for Log4j API .. SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 29.063 s
[INFO] Finished at: 2017-02-03T11:00:55-08:00
[INFO] Final Memory: 49M/691M
[INFO]

[ERROR] 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]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Thoughts?

Gary

On Fri, Feb 3, 2017 at 10:06 AM, Gary Gregory 
wrote:

> If I @Ignore that one test, then I get (mvn clean install):
>
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842 sec
> - in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBundleTest
> at org.junit.internal.runners.statements.InvokeMethod.
> evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.
> evaluate(RunBefores.java:26)
> at org.junit.rules.ExternalResource$1.evaluate(
> ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(
> BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(
> ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(
> ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(
> JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.
> executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.
> executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(
> JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.
> invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.
> runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(
> ForkedBooter.java:121)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.logging.log4j.core.util.ExecutorServices not found by
> org.apache.logging.log4j.api [1]
> at org.apache.felix.framework.BundleWiringImpl.
> findClassOrResourceByDelegation(BundleWiringImpl.java:1558)
> at org.apache.felix.framework.BundleWiringImpl.access$400(
> BundleWiringImpl.java:79)
> at org.apache.felix.framework.BundleWiringImpl$
> BundleClassLoader.loadClass(BundleWiringImpl.java:1998)
> ... 45 more
> Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, 

Re: RollingAppenderSizeTest failures

[Gary Gregory]

If I @Ignore that one test, then I get (mvn clean install):

Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.842 sec -
in org.apache.logging.log4j.osgi.tests.equinox.EquinoxLoadApiBundleTest
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.util.ExecutorServices not found by
org.apache.logging.log4j.api [1]
at
org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1558)
at
org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79)
at
org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1998)
... 45 more
Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.048 sec
<<< FAILURE! - in
org.apache.logging.log4j.osgi.tests.felix.FelixLoadApiBundleTest
testClassNotFoundErrorLogger(org.apache.logging.log4j.osgi.tests.felix.FelixLoadApiBundleTest)
 Time elapsed: 0.419 sec  <<< ERROR!
org.osgi.framework.BundleException: Error creating bundle cache.
Caused by: java.lang.Exception: Unable to lock bundle cache:
java.nio.channels.OverlappingFileLockException


Results :

Tests in error:
  FelixLoadApiBundleTest.testClassNotFoundErrorLogger ╗ Bundle Error
creating bu...

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

[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 . SUCCESS [
 1.847 s]
[INFO] Apache Log4j API ... SUCCESS [
18.399 s]
[INFO] Apache Log4j Core .. SUCCESS [18:01
min]
[INFO] Apache Log4j 1.x Compatibility API . SUCCESS [
 9.090 s]
[INFO] Apache Log4j SLF4J Binding . SUCCESS [
 5.460 s]
[INFO] Apache Log4j to SLF4J Adapter .. SUCCESS [
 3.202 s]
[INFO] Apache Log4j Commons Logging Bridge  SUCCESS [
 2.712 s]
[INFO] Apache Log4j Flume Bridge .. SUCCESS [
38.267 s]
[INFO] Apache Log4j Web ... SUCCESS [
 6.096 s]
[INFO] Apache Log4j Tag Library ... SUCCESS [
15.773 s]
[INFO] Apache Log4j JMX GUI ... SUCCESS [
 1.741 s]
[INFO] Apache Log4j Samples ... SUCCESS [
 0.499 s]
[INFO] Apache Log4j Samples: Flume - Common ... SUCCESS [
 2.257 s]
[INFO] Apache Log4j Samples: Flume - Remote ... SUCCESS [
 2.679 s]
[INFO] Apache Log4j Samples: Flume - Embedded . SUCCESS [
 6.387 s]
[INFO] Apache Log4j Samples: Configuration  SUCCESS [
 2.592 s]
[INFO] Apache Log4j Samples: LoggerProperties . SUCCESS [
 2.703 s]
[INFO] Apache Log4j Scala 2.11 wrapper for Log4j API .. SUCCESS [
25.789 s]
[INFO] Apache Log4j Samples: Scala API  SUCCESS [
 4.300 s]
[INFO] Apache Log4j OSGi .. FAILURE [
 8.806 s]
[INFO] Apache Log4j BOM ... SKIPPED
[INFO] Apache Log4j NoSQL . SKIPPED
[INFO] Apache Log4J Performance Tests . SKIPPED
[INFO] Apache Log4j Streaming Interface ... 

Re: SyslogAppender parameter name change

[Matt Sicker]

Plugins can have aliases via @PluginAliases (see for example <
https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/mom/JmsAppender.java>),
don't recall if attributes are supported. If not, that's a feature we can
support for sure.

On 2 February 2017 at 18:27, Gary Gregory  wrote:

> Darn, I apologize for that one.
>
> Gary
>
> On Thu, Feb 2, 2017 at 4:09 PM, Remko Popma  wrote:
>
>> Sorry for that and thanks for letting us know!
>>
>> I wonder if parameter names can have aliases so we can support both the
>> old and the new name without causing users inconvenience. If possible we
>> should address this for 2.8.1.
>>
>> Remko
>>
>> Sent from my iPhone
>>
>> On Feb 3, 2017, at 4:13, Sam Beroz  wrote:
>>
>> The reconnectionDelayMillis parameter was renamed
>> to reconnectDelayMillis. After updating to release 2.8 I noticed that I was
>> getting the following error:
>>
>> ERROR Syslog contains an invalid element or attribute
>> "reconnectionDelayMillis"
>>
>>
>> It appears that change was part of this commit:
>>
>> commit ed828be67a23ee3513cafc9d2fd0ff16a26c7013
>> Author: Gary Gregory 
>> Date:   Mon Nov 14 15:11:47 2016 -0800
>>
>> [LOG4J2-1709]
>>
>> Add a Builder to SyslogAppender and deprecate
>> SyslogAppender.createAppender().
>>
>>
>>
>> The documentation (https://logging.apache.org/lo
>> g4j/2.x/manual/appenders.html#SyslogAppender) still has the parameter
>> listed as "reconnectionDelayMillis" but the code is now obviously
>> looking for "reconnectDelayMillis". I'm going to change my config to use
>> the new name, but I thought I'd point out the disconnect as it had me
>> confused for a bit. Thanks - Sam
>>
>>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
>
> 
> JUnit in Action, Second Edition
> 
>
> 
> Spring Batch in Action
> 
> 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker