[jira] [Updated] (LOG4J2-1793) Why there can't get thrown from LogEvent

[ https://issues.apache.org/jira/browse/LOG4J2-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] elkan updated LOG4J2-1793: -- Description: There I want create a customer defined appender and need get stack case message. So in over write

[jira] [Created] (LOG4J2-1793) Why there can't get thrown from LogEvent

elkan created LOG4J2-1793: - Summary: Why there can't get thrown from LogEvent Key: LOG4J2-1793 URL: https://issues.apache.org/jira/browse/LOG4J2-1793 Project: Log4j 2 Issue Type: Bug Compon

[jira] [Updated] (LOG4J2-1791) Timezone support in JSONLayout

[ https://issues.apache.org/jira/browse/LOG4J2-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shubham aggarwal updated LOG4J2-1791: - Priority: Minor (was: Major) > Timezone support in JSONLayout >

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829160#comment-15829160 ] Jan commented on LOG4J2-1182: - Thank you for the hint regarding recursion [~rem...@yahoo.com]

Re: Any opposition to requesting git->jira integration?

Ok, thank you. Let's see how it goes. I still think the emails from the git2jira comments (or the comments themselves) tend not to be very informative. :-) I appreciate your taking action quickly! Remko Sent from my iPhone > On Jan 19, 2017, at 1:20, Matt Sicker wrote: > > I just requested

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828874#comment-15828874 ] Remko Popma commented on LOG4J2-1182: - About the recursion, the configuration is {{ig

Jenkins build is unstable: Log4j 2.x #2617

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

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828764#comment-15828764 ] Jan commented on LOG4J2-1182: - One more observation: The error was persistent. I mean it star

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828758#comment-15828758 ] Jan commented on LOG4J2-1182: - {quote} Jan, Does the issue also occur with 2.7? {quote} Hi [~

[jira] [Resolved] (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:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1748. Resolution: Fixed In Git master. Please verify (again) and close. > RollingFile appender

[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=15828646#comment-15828646 ] ASF subversion and git services commented on LOG4J2-1748: - Commit

[jira] [Resolved] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal resolved LOG4J2-1780. Resolution: Fixed in Git master > Eliminate the use of the ExecutorServices in the LoggerC

[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=15828649#comment-15828649 ] ASF subversion and git services commented on LOG4J2-1748: - Commit

[jira] [Commented] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828647#comment-15828647 ] ASF subversion and git services commented on LOG4J2-1780: - Commit

[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=15828648#comment-15828648 ] ASF subversion and git services commented on LOG4J2-1748: - Commit

[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=15828651#comment-15828651 ] ASF GitHub Bot commented on LOG4J2-1748: Github user asfgit closed the pull reque

[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=15828495#comment-15828495 ] ASF GitHub Bot commented on LOG4J2-1748: Github user rgoers commented on the issu

Re: Any opposition to requesting git->jira integration?

The email spam issue from merges to topic branches is apparently something Infra is already working on in general, so we should hopefully see some improvements on that in the next month or so. On 18 January 2017 at 10:20, Matt Sicker wrote: > I just requested that they only enable the git2jira i

[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=15828492#comment-15828492 ] ASF GitHub Bot commented on LOG4J2-1748: Github user jvz commented on the issue:

Re: github

I’m not trying to merge anything at this point. I am only trying to indicate that I have reviewed the code and am OK to have it committed. I have now found how to do that. Thanks! Ralph > On Jan 18, 2017, at 9:45 AM, Stefan Bodewig wrote: > > Sorry for the comment from the outside. > > Acce

Re: github

Thank you! That was exactly what I was looking for. Ralph > On Jan 18, 2017, at 9:43 AM, Mikael Ståldal wrote: > > It should be possible to accept the PR without making any comment. Just go do > the "Files changed" tab, click on "Review change" (upper-right) and choose > "Approve". > > On

Re: Remaining tasks for a 2.8 release

JIRA issue for Log4j 1.x property substitution: https://issues.apache.org/jira/browse/LOG4J2-1792 On Wed, Jan 18, 2017 at 1:51 PM, Mikael Ståldal wrote: > I think that Log4j1ConfigurationConverter does not handle Log4j 1.x > property substitution correctly. Log4j 1.x let you override properties

[jira] [Created] (LOG4J2-1792) Support property substitution when reading Log4j 1.x property config files

Mikael Ståldal created LOG4J2-1792: -- Summary: Support property substitution when reading Log4j 1.x property config files Key: LOG4J2-1792 URL: https://issues.apache.org/jira/browse/LOG4J2-1792 Projec

ApacheCon CFP closing soon (11 February)

Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been puttin

Re: github

Sorry for the comment from the outside. Accepting a PR is only a matter of merging the commits or using something like "git am" on a file you create from the PR by appending .patch - e.g. https://github.com/apache/logging-log4j2/pull/53.patch If you do so, this will not close the PR, though. You

Re: github

It should be possible to accept the PR without making any comment. Just go do the "Files changed" tab, click on "Review change" (upper-right) and choose "Approve". On Wed, Jan 18, 2017 at 5:36 PM, Ralph Goers wrote: > So I can't accept the PR unless I have made at least one comment? > > Ralph >

[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=15828378#comment-15828378 ] ASF subversion and git services commented on LOG4J2-1748: - Commit

[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=15828375#comment-15828375 ] ASF subversion and git services commented on LOG4J2-1748: - Commit

[jira] [Commented] (LOG4J2-1780) Eliminate the use of the ExecutorServices in the LoggerContext

[ https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828376#comment-15828376 ] ASF subversion and git services commented on LOG4J2-1780: - Commit

[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=15828377#comment-15828377 ] ASF subversion and git services commented on LOG4J2-1748: - Commit

[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=15828379#comment-15828379 ] ASF GitHub Bot commented on LOG4J2-1748: Github user mikaelstaldal commented on a

Re: github

So I can't accept the PR unless I have made at least one comment? Ralph > On Jan 18, 2017, at 9:08 AM, Matt Sicker wrote: > > The commit count statistics have always been a silly function of GitHub. See > for example . > > As for reviewing PRs, you just

Re: Any opposition to requesting git->jira integration?

I just requested that they only enable the git2jira integration for master. I also requested if we can get rid of merge commit emails on topic branches or if we can just disable non-master commits from spamming the list. I find that it's nearly impossible to review a topic branch via those commit m

Re: Any opposition to requesting git->jira integration?

The merging master to topic branches causing commit messages on the list is the real problem here I think. I'll make a couple infra requests to try and reduce some spamminess. On 18 January 2017 at 05:40, Remko Popma wrote: > +1 > > It seemed like a good idea but I have trouble keeping up. Too m

Re: Remaining tasks for a 2.8 release

Ralph, you can add yourself as a reviewer on GitHub by commenting on a line in the diff. It should offer you the ability to start a review then. On 18 January 2017 at 08:17, Apache wrote: > That will probably cover 80% of the use cases. Another option is to use a > proxy factory that reads the f

Re: github

The commit count statistics have always been a silly function of GitHub. See for example . As for reviewing PRs, you just click a line to add a comment, and it offers to start a review or just add a single comment at a time. It should let you do it; anyone ca

[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=15828319#comment-15828319 ] ASF GitHub Bot commented on LOG4J2-1748: Github user jvz commented on a diff in t

[jira] [Comment Edited] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828277#comment-15828277 ] Remko Popma edited comment on LOG4J2-1182 at 1/18/17 3:33 PM: -

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828277#comment-15828277 ] Remko Popma commented on LOG4J2-1182: - ~hbgj, Does the issue also occur with 2.7? >

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

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris McGee closed LOG4J2-1640. --- Looks like the fix is working. I'll still keep an eye on it, of course, just in case. > RollingFileAppe

[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=15828254#comment-15828254 ] Chris McGee commented on LOG4J2-1640: - Looks good. I'll go ahead and close this issue

Re: Remaining tasks for a 2.8 release

That will probably cover 80% of the use cases. Another option is to use a proxy factory that reads the file and determines if logger.rootLogger or logger.appender is present and routes to the Log4j1ConfigurationFactory if it is and the Log4j2 factory if it is not. Ralph > On Jan 18, 2017, at 6

[jira] [Commented] (LOG4J2-1182) RandomAccessFile IOException: Stream Closed is back

[ https://issues.apache.org/jira/browse/LOG4J2-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828092#comment-15828092 ] Jan commented on LOG4J2-1182: - We had the same issue recently with version 2.5: {noformat} 15

[jira] [Created] (LOG4J2-1791) Timezone support in JSONLayout

shubham aggarwal created LOG4J2-1791: Summary: Timezone support in JSONLayout Key: LOG4J2-1791 URL: https://issues.apache.org/jira/browse/LOG4J2-1791 Project: Log4j 2 Issue Type: New Feat

Re: Remaining tasks for a 2.8 release

FYI, it seems to me that if Log4j1ConfigurationFactory has SUFFIXES = { "log4j.properties"}, then it would not clash with log4j2.properties file but could still work as one of the automatic configuration factories. On Wed, Jan 18, 2017 at 9:51 PM, Mikael Ståldal wrote: > I think that Log4j1Confi

Re: github

Yes, I have an account and yes I am a member of the org. I also have my username specified at Id.apache.org. Ralph > On Jan 17, 2017, at 11:03 PM, Gary Gregory wrote: > > The repo is read-only, so it's only useful for people who like GitHub instead > of svn and who do not have commit rights t

Re: Remaining tasks for a 2.8 release

I think that Log4j1ConfigurationConverter does not handle Log4j 1.x property substitution correctly. Log4j 1.x let you override properties with Java System Properties, but Log4j 2.x only do that when you specify ${sys:key}. Right? So the converter needs to convert from ${key} to ${sys:key}, and al

[jira] [Commented] (LOG4J2-1255) Logger.entry and Logger.exit should support Messages.

[ https://issues.apache.org/jira/browse/LOG4J2-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827974#comment-15827974 ] Mikael Ståldal commented on LOG4J2-1255: Can this issue be closed? > Logger.entr

[jira] [Commented] (LOG4J2-1648) Provide ability for users to put non-String values in the ThreadContext

[ https://issues.apache.org/jira/browse/LOG4J2-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827959#comment-15827959 ] Remko Popma commented on LOG4J2-1648: - To answer Mikael's question on the mailing lis

Re: Any opposition to requesting git->jira integration?

+1 It seemed like a good idea but I have trouble keeping up. Too many emails... I already have trouble keeping up with the commit emails and the list traffic, and these JIRA entries add more traffic that don't really tell me anything new. What do you think? Sent from my iPhone > On Jan 18,

Re: Remaining tasks for a 2.8 release

For Log4j 1 config support, we need to go through the Log4j 1 appenders and see how to map them to Log4j 2 appenders, or reimplement in Log4j 2 if not possible to map. See https://issues.apache.org/jira/browse/LOG4J2-1523 (Layouts are already done: https://issues.apache.org/jira/browse/LOG4J2-1522

[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=15827720#comment-15827720 ] ASF GitHub Bot commented on LOG4J2-1748: Github user mikaelstaldal commented on a

Re: Remaining tasks for a 2.8 release

Maybe Matt can describe how he got added as reviewer? I cannot test it myself since GitHub forbids review of your own PR:s. On Wed, Jan 18, 2017 at 2:10 AM, Apache wrote: > How do I add myself as a reviewer? > > Ralph > > On Jan 17, 2017, at 2:05 PM, Mikael Ståldal > wrote: > > OK, Pull Request

[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=15827671#comment-15827671 ] ASF GitHub Bot commented on LOG4J2-1748: Github user mikaelstaldal commented on t

Re: Remaining tasks for a 2.8 release

What is left to do on LOG4J2-1648 ? Only documentation? On Wed, Jan 18, 2017 at 2:10 AM, Apache wrote: > How do I add myself as a reviewer? > > Ralph > > On Jan 17, 2017, at 2:05 PM, Mikael Ståldal > wrote: > > OK, Pull Request here: > > https

Re: Any opposition to requesting git->jira integration?

It seems to be a bit spammy though. When I merged master into my branch, all those commits trigger notification again. Can we maybe restrict it to only monitor master branch? On Mon, Jan 16, 2017 at 12:29 AM, Matt Sicker wrote: > It appears this feature is enabled and working. > > On 15 January