Re: [1/2] logging-log4j2 git commit: Fixed concurrency issue affecting all layouts except PatternLayout and GelfLayout, which caused scrambled output and exceptions when logging synchronously from mul

Sorry. I haven't been able to fix this. It passes on my Windows machine. It has something to do with the path of the log file, I don't understand why target/test-json-layout.log can't be found on unix systems... I'm thinking to just comment out that part of the test... Sent from my iPhone >

Re: [1/2] logging-log4j2 git commit: Fixed concurrency issue affecting all layouts except PatternLayout and GelfLayout, which caused scrambled output and exceptions when logging synchronously from mul

ConcurrentLoggingWithJsonLayoutTest is failing for me. I don’t understand why. 2017-01-09 21:41:06,174 main DEBUG Starting LoggerContext[name=org.apache.logging.log4j.core.layout.ConcurrentLoggingWithJsonLayoutTest] from configuration at log4j2-json-layout.xml 2017-01-09 21:41:06,176 main DEBUG

Jenkins build is still unstable: Log4j 2.x #2592

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Description: This is the main feature for the Log4j Boot epic (LOG4J2-1775). {code} groupId: org.a

Re: Log4j Boot

Ok, I think it would've been annoying to match the version numbers. However, each version of Log4j Boot will need to be released with updated versions of Log4j anyways. On 9 January 2017 at 21:45, Apache wrote: > Please don’t try to match the Log4j version numbers. That would mean we > would hav

Re: Log4j Boot

Please don’t try to match the Log4j version numbers. That would mean we would have to release them along with each Log4j release, which probably won’t be necessary. I would make the first release -beta, unless you think the first 1.0 release will be where it needs to be. Ralph > On Jan 9, 201

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Oh, I totally forgot about OpenDNS. I thought they did redirects, too. On 9 January 2017 at 21:37, Apache wrote: > OK. I called Cox and they gave me the ip addresses that don’t redirect but > I was still getting their ipv6 DNS that does. I had to set that to go to > OpenDNS instead (see https://

Log4j Boot

So I'm going to go with this name as it's pretty self-explanatory what it's for. https://git-wip-us.apache.org/repos/asf/logging-log4j-boot.git Quick question: should these version numbers match the log4j versions? Or can this follow its own versioning scheme starting with 1.0? -- Matt Sicker

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

OK. I called Cox and they gave me the ip addresses that don’t redirect but I was still getting their ipv6 DNS that does. I had to set that to go to OpenDNS instead (see https://www.opendns.com/about/innovations/ipv6/ ). Now the test passes. Ralph

[jira] [Closed] (LOG4J2-1778) Add logging-log4j-boot git repo

[ https://issues.apache.org/jira/browse/LOG4J2-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-1778. --- Resolution: Fixed https://git-wip-us.apache.org/repos/asf/logging-log4j-boot.git > Add logging-log4j

Jenkins build is still unstable: Log4j 2.x #2591

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Updated] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-boot module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1777: Description: Add JUnit {{@Category}} [annotations|https://github.com/junit-team/junit4/wiki/Categor

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

I'm trying an invalid IP address instead. If that still doesn't work, then I'll add an Assume.assumeThat() to the test so it's ignored with weird DNS servers. A lot of people like 8.8.8.8 (Google) and 4.2.2.2 (Level3) for DNS. There's also 75.75.75.75 which is Comcast (or 2001:558:feed::1 which is

[jira] [Updated] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-boot module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1777: Summary: Add JUnit categories to integration tests for use in log4j-boot module test suites (was:

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

It appears I need to use a different DNS server for it to stop redirecting me. I need to figure out which one to use. Ralph > On Jan 9, 2017, at 7:34 PM, Apache wrote: > > > Didn’t run the test. Don’t really have to. > > nslookup "#$%^&*(*&^%$" > Server: 2001:578:3f::30 > Addre

[jira] [Assigned] (LOG4J2-1777) Add JUnit categories to integration tests for use in log4j-starter module test suites

[ https://issues.apache.org/jira/browse/LOG4J2-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker reassigned LOG4J2-1777: --- Assignee: Matt Sicker > Add JUnit categories to integration tests for use in log4j-starter m

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Didn’t run the test. Don’t really have to. nslookup "#$%^&*(*&^%$" Server: 2001:578:3f::30 Address:2001:578:3f::30#53 Non-authoritative answer: Name: #\$%^&*\(*&^%\$ Address: 92.242.140.2 Ralph > On Jan 9, 2017, at 7:31 PM, Matt Sicker wrote: > > Let me know if my update

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Let me know if my updated test still causes issues. On 9 January 2017 at 20:30, Apache wrote: > I suspect this is my ISP at work. When I enter an invalid domain I get a > web site from cox.net saying it can’t find the domain and it offers > suggestions for other sites. > > I think this test has

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

I suspect this is my ISP at work. When I enter an invalid domain I get a web site from cox.net saying it can’t find the domain and it offers suggestions for other sites. I think this test has to be removed. Ralph > On Jan 9, 2017, at 7:28 PM, Matt Sicker wrote: > > Well te

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Well technically a UUID can be a valid hostname itself besides being interpreted as a hex-encoded IP address (if the rest of it gets chopped off). I've updated the test to use a jumble of invalid hostname characters instead. On 9 January 2017 at 20:26, Apache wrote: > nslookup dcc071ab-bc05-46ed

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

nslookup dcc071ab-bc05-46ed-bfc0-be5fe876f6ea Server: 2001:578:3f::30 Address:2001:578:3f::30#53 Non-authoritative answer: Name: dcc071ab-bc05-46ed-bfc0-be5fe876f6ea Address: 92.242.140.2 > On Jan 9, 2017, at 7:24 PM, Matt Sicker wrote: > > I suppose technically the first pa

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

I suppose technically the first part of a UUID can be an IPv4 address encoded in hex. I'll make a better invalid value. On 9 January 2017 at 20:20, Apache wrote: > Debugging this and InetAddress.getByName is returning an InetAddress > object. The value is > Host: dcc071ab-bc05-46ed-bfc0-be5fe876

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Running it again I obviously get a different host address but the same IP address is returned. Ralph > On Jan 9, 2017, at 7:20 PM, Apache wrote: > > Debugging this and InetAddress.getByName is returning an InetAddress object. > The value is > Host: dcc071ab-bc05-46ed-bfc0-be5fe876f6ea > Addre

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Debugging this and InetAddress.getByName is returning an InetAddress object. The value is Host: dcc071ab-bc05-46ed-bfc0-be5fe876f6ea Address: 92.242.140.2 Ralph > On Jan 9, 2017, at 7:12 PM, Matt Sicker wrote: > > Not sure how that's possible, but I added a better assert message. Let me > kno

[jira] [Created] (LOG4J2-1778) Add logging-log4j-boot git repo

Matt Sicker created LOG4J2-1778: --- Summary: Add logging-log4j-boot git repo Key: LOG4J2-1778 URL: https://issues.apache.org/jira/browse/LOG4J2-1778 Project: Log4j 2 Issue Type: New Git Repo

[jira] [Updated] (LOG4J2-1775) Log4j Boot modules for easy dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1775: Summary: Log4j Boot modules for easy dependency management (was: Add boot pom files for dependency

Re: How about a log4j-starters sort of repository?

Going to go with the name Log4j Boot. I submitted a git repo request and the form says it should be created within the hour. On 8 January 2017 at 23:13, Apache wrote: > Go for it! > > Ralph > > On Jan 8, 2017, at 1:44 PM, Matt Sicker wrote: > > Also, one neat aspect of this that I didn't think

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Description: This is the main feature for the Log4j Boot epic (LOG4J2-1775). {code} groupId: org.a

[jira] [Updated] (LOG4J2-1776) log4j-boot pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1776: Summary: log4j-boot pom modules for dependency management (was: log4j-starter pom modules for depe

[jira] [Updated] (LOG4J2-1775) Add boot pom files for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1775: - Summary: Add boot pom files for dependency management (was: Add starter pom files for dependency

[jira] [Updated] (LOG4J2-1775) Add starter pom files for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker updated LOG4J2-1775: Epic Name: Log4j Boot (was: Log4j Starters) > Add starter pom files for dependency management > --

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

Not sure how that's possible, but I added a better assert message. Let me know if you're still having an issue with it. Is it a failure from IntelliJ or Maven? On 9 January 2017 at 19:47, Apache wrote: > This commit appears to be failing for me. The testInvalidIpAddress method > is failing on th

Re: logging-log4j2 git commit: [LOG4J2-1755]: Add converters and validators for hostnames/ports

This commit appears to be failing for me. The testInvalidIpAddress method is failing on the assert. Ralph > On Dec 30, 2016, at 2:01 PM, [email protected] wrote: > > Repository: logging-log4j2 > Updated Branches: > refs/heads/master 367d26b09 -> 4254e2558 > > > [LOG4J2-1755]: Add convert

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813291#comment-15813291 ] Ralph Goers commented on LOG4J2-1776: - +1 for log4j-boot. > log4j-starter pom module

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813255#comment-15813255 ] Matt Sicker commented on LOG4J2-1776: - For brevity's sake, "log4j-boot" is even bette

[jira] [Commented] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813191#comment-15813191 ] Gary Gregory commented on LOG4J2-1768: -- Please do try 2.7. Gary > MDC.clear() is b

[jira] [Commented] (LOG4J2-1776) log4j-starter pom modules for dependency management

[ https://issues.apache.org/jira/browse/LOG4J2-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813100#comment-15813100 ] Gary Gregory commented on LOG4J2-1776: -- Would the prefix "log4j-start" also be accep

[jira] [Commented] (LOG4J2-1713) Allow for more general serialization of Log4j2 configurations

[ https://issues.apache.org/jira/browse/LOG4J2-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812998#comment-15812998 ] Kurt Seidel commented on LOG4J2-1713: - Thanks for the reply. I think that answers my

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812875#comment-15812875 ] Matt Sicker commented on LOG4J2-1640: - Oh ok, got it. > RollingFileAppender with Cro

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812841#comment-15812841 ] Ralph Goers commented on LOG4J2-1640: - No. As I said, System.nanotime() is relative t

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812770#comment-15812770 ] Matt Sicker commented on LOG4J2-1640: - Couldn't you use {{new Date(TimeUnit.NANOS.toM

Jenkins build is still unstable: Log4j 2.x #2590

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Resolved] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1640. - Resolution: Fixed Fix Version/s: 2.8 Please verify and close. > RollingFileAppender with

[jira] [Commented] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812045#comment-15812045 ] Ralph Goers commented on LOG4J2-1640: - So it turns out that the ScheduledExecutorServ

Re: Property vs. KeyValuePair

Properties are automatically interpolated and used as interpolatable values while KeyValuePairs are not (at least IIRC). Basically, it seems to be a semantic difference. On 9 January 2017 at 04:43, Remko Popma wrote: > They seem similar, but slightly different usage: KeyValuePair is used in > Fi

Re: Property vs. KeyValuePair

They seem similar, but slightly different usage: KeyValuePair is used in Filters and Layouts (via LoggerFields), where Property is used in Configuration and some Appenders. Otherwise they seem structurally very similar. Some historical reason? Sent from my iPhone > On Jan 9, 2017, at 17:54,

Re: Bug in Async Logger?

Should be contextData.put(prop.getName(), value); I can fix it. Sent from my iPhone > On Jan 9, 2017, at 19:27, Mikael Ståldal wrote: > > Will you fix it? I am not sure I know how it is supposed to be. > >> On Jan 9, 2017 10:10 AM, "Remko Popma" wrote: >> Yes that's a bug. >> Well spotted! >

Re: Bug in Async Logger?

Will you fix it? I am not sure I know how it is supposed to be. On Jan 9, 2017 10:10 AM, "Remko Popma" wrote: > Yes that's a bug. > Well spotted! > > Sent from my iPhone > > > On Jan 9, 2017, at 17:50, Mikael Ståldal > wrote: > > > > Have a look at AsyncLogger.java 328-331. "value" is not used,

Jenkins build is still unstable: Log4j 2.x #2589

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811361#comment-15811361 ] Remko Popma commented on LOG4J2-1724: - Nice! > Using variables in GelfLayout's addit

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811186#comment-15811186 ] Remko Popma commented on LOG4J2-1748: - I think it's a good idea to use the {{config.g

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811165#comment-15811165 ] Remko Popma commented on LOG4J2-1748: - ... and another good catch! Two actually. Log

Re: Bug in Async Logger?

Yes that's a bug. Well spotted! Sent from my iPhone > On Jan 9, 2017, at 17:50, Mikael Ståldal wrote: > > Have a look at AsyncLogger.java 328-331. "value" is not used, is that correct? - To unsubscribe, e-mail: log4j-dev-unsu

[jira] [Commented] (LOG4J2-1724) Using variables in GelfLayout's additional fields at runtime

[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811123#comment-15811123 ] Mikael Ståldal commented on LOG4J2-1724: OK. I managed to keep it gc-free with ad

Property vs. KeyValuePair

What is the difference between classes Property and KeyValuePair?

Bug in Async Logger?

Have a look at AsyncLogger.java 328-331. "value" is not used, is that correct?

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811075#comment-15811075 ] Mikael Ståldal commented on LOG4J2-1748: Anyway, we could change "shutdownTimeout

[jira] [Commented] (LOG4J2-1748) RollingFile appender prevents a stand alone application to terminate for as long as 60 sec

[ https://issues.apache.org/jira/browse/LOG4J2-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15811073#comment-15811073 ] Mikael Ståldal commented on LOG4J2-1748: I don't really understand why we can't u