[jira] [Updated] (LOG4J2-1521) StringIndexOutOfBoundsException thrown when rolling logs

[ https://issues.apache.org/jira/browse/LOG4J2-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johno Crawford updated LOG4J2-1521: --- Attachment: log4j2-events.zip > StringIndexOutOfBoundsException thrown when rolling logs > --

[jira] [Updated] (LOG4J2-1521) StringIndexOutOfBoundsException thrown when rolling logs

[ https://issues.apache.org/jira/browse/LOG4J2-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johno Crawford updated LOG4J2-1521: --- Environment: Windows 10 Pro 64-bit (10.0, Build 14393) (14393.rs1_release.160715-1616) java

[jira] [Created] (LOG4J2-1521) StringIndexOutOfBoundsException thrown when rolling logs

Johno Crawford created LOG4J2-1521: -- Summary: StringIndexOutOfBoundsException thrown when rolling logs Key: LOG4J2-1521 URL: https://issues.apache.org/jira/browse/LOG4J2-1521 Project: Log4j 2

Jenkins build is back to stable : Log4j 2.x #2168

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

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

That's right. (I've never needed static import for any thing else in Log4j. ) Sent from my iPhone > On 2016/08/16, at 13:02, Matt Sicker wrote: > > If I recall correctly, the IDE settings committed into the repo a while back > had * imports for org.junit.Assert.* and org.hamcrest.Matchers.*,

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

If I recall correctly, the IDE settings committed into the repo a while back had * imports for org.junit.Assert.* and org.hamcrest.Matchers.*, and non-wildcard static imports for everything else. On 15 August 2016 at 20:22, Remko Popma wrote: > Maybe I had it the wrong way around, because at the

Jenkins build became unstable: Log4j 2.x #2167

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

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

Maybe I had it the wrong way around, because at the moment looks like your formatter converts * to individual static imports... Sent from my iPhone > On 2016/08/16, at 10:16, Gary Gregory wrote: > > Nevermind, I will leave it at 99 since we do not want *'s for anything less > that 99. > > Ga

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

Nevermind, I will leave it at 99 since we do not want *'s for anything less that 99. Gary On Mon, Aug 15, 2016 at 6:16 PM, Gary Gregory wrote: > Odd, mine is set to 99 for static imports, I'll set it to 1 for statics. > > Gary > > On Mon, Aug 15, 2016 at 5:44 PM, Remko Popma > wrote: > >> I us

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

Odd, mine is set to 99 for static imports, I'll set it to 1 for statics. Gary On Mon, Aug 15, 2016 at 5:44 PM, Remko Popma wrote: > I use a high number to ensure all static imports are wildcarts. > (Thanks for the correction, I wrote from memory and had it the wrong way > around.) > > Sent from

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

I use a high number to ensure all static imports are wildcarts. (Thanks for the correction, I wrote from memory and had it the wrong way around.) Sent from my iPhone > On 2016/08/16, at 7:46, Matt Sicker wrote: > > Is there a minimum number of imports before going to *, or are we just using

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

Is there a minimum number of imports before going to *, or are we just using a really high number like 100 to prevent it altogether? On 15 August 2016 at 17:45, Remko Popma wrote: > Gary, you may have upgraded your IDE and forgotten to change the static > import threshold to 1 in the formatter.

Re: logging-log4j2 git commit: [LOG4J2-1516] Add ThreadContextMap.putAll(Map).

Gary, you may have upgraded your IDE and forgotten to change the static import threshold to 1 in the formatter. > +import static org.junit.Assert.assertEquals; > +import static org.junit.Assert.assertFalse; > +import static org.junit.Assert.assertNull; > +import static org.junit.Assert.assertTru

[jira] [Reopened] (LOG4J2-1519) Add ThreadContext.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1519: - Reopening. No time to write much comment. Please refer to my comments on the ticket Gary referred to

[jira] [Commented] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421815#comment-15421815 ] Remko Popma commented on LOG4J2-1516: - I guess I can add this method to the new data

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421808#comment-15421808 ] Remko Popma commented on LOG4J2-1259: - In my previous comment I asked for additional

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421801#comment-15421801 ] Remko Popma commented on LOG4J2-1447: - Well spotted. In the branch they are matched n

[jira] [Commented] (LOG4J2-1518) Deadlock when using pure async and toString logs another message

[ https://issues.apache.org/jira/browse/LOG4J2-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421791#comment-15421791 ] Remko Popma commented on LOG4J2-1518: - I'll take a look at this when I get back from

Jenkins build is back to normal : Log4j 2.x #2165

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

[jira] [Comment Edited] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421514#comment-15421514 ] Gary Gregory edited comment on LOG4J2-1517 at 8/15/16 10:00 PM: ---

Build failed in Jenkins: Log4j 2.x #2164

See Changes: [ggregory] Forgot to remove import. [ggregory] Use a ThreadContextRule to clean up tests. -- [...truncated 3771 lines...] [JENKINS] Recording test results [INFO] [INFO] --- maven-bund

Build failed in Jenkins: Log4j 2.x #2163

See Changes: [ggregory] [LOG4J2-1516] Add ThreadContextMap.putAll(Map). [ggregory] [LOG4J2-1516] Add ThreadContextMap.putAll(Map). [ggregory] [LOG4J2-1519] Add ThreadContext.putAll(Map). [ggregory] [LOG4J2-1520] Add JUnit Rule implementa

[jira] [Closed] (LOG4J2-1520) Add JUnit Rule implementations to manage the thread context

[ https://issues.apache.org/jira/browse/LOG4J2-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1520. Resolution: Fixed In Git master. > Add JUnit Rule implementations to manage the thread context > -

[jira] [Created] (LOG4J2-1520) Add JUnit Rule implementations to manage the thread context

Gary Gregory created LOG4J2-1520: Summary: Add JUnit Rule implementations to manage the thread context Key: LOG4J2-1520 URL: https://issues.apache.org/jira/browse/LOG4J2-1520 Project: Log4j 2

[jira] [Closed] (LOG4J2-1519) Add ThreadContext.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1519. Resolution: Fixed This surfaces the new {{ThreadContextMap.putAll(Map}} API with the same name to

[jira] [Closed] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1516. Resolution: Fixed This lower-level API does not seem to trigger a discussion unlike {{ThreadContex

[jira] [Created] (LOG4J2-1519) Add ThreadContext.putAll(Map)

Gary Gregory created LOG4J2-1519: Summary: Add ThreadContext.putAll(Map) Key: LOG4J2-1519 URL: https://issues.apache.org/jira/browse/LOG4J2-1519 Project: Log4j 2 Issue Type: New Feature

[jira] [Updated] (LOG4J2-1519) Add ThreadContext.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1519: - Description: Add API {{ThreadContext.putAll(Map)}}. My immediate goal is to be able to build a J

[jira] [Comment Edited] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421514#comment-15421514 ] Gary Gregory edited comment on LOG4J2-1517 at 8/15/16 7:24 PM:

[jira] [Commented] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421514#comment-15421514 ] Gary Gregory commented on LOG4J2-1517: -- Would this be a different kind of problem fr

[jira] [Commented] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421353#comment-15421353 ] Ralph Goers commented on LOG4J2-1517: - I'm fine with the "one at a time' method. If t

[jira] [Commented] (LOG4J2-1419) Memory leak on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421303#comment-15421303 ] Mickael Marrache commented on LOG4J2-1419: -- Any news with this issue? > Memory

[jira] [Commented] (LOG4J2-1259) Log4j threads are leaking on tomcat shutdown

[ https://issues.apache.org/jira/browse/LOG4J2-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421302#comment-15421302 ] Mickael Marrache commented on LOG4J2-1259: -- Any news with this issue? > Log4j t

[jira] [Commented] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421239#comment-15421239 ] Gary Gregory commented on LOG4J2-1517: -- I have an alternate implementation of the ho

[jira] [Updated] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1517: - Description: Add {{Add ThreadContext.setContext(Map)}}. Note that we have {{ThreadContext.setSta

[jira] [Updated] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1517: - Description: Add {{Add ThreadContext.setContext(Map)}}. Note that we have {{ThreadContext.setSta

Re: Migrating from Log4j 1

Printing out the equivalent Log4j2 configuration would be nice. Probably not trivial, but we should try to do that. On Mon, Aug 15, 2016 at 12:55 PM, Remko Popma wrote: > I would be okay with that, but I'd like to print out a warning message and > the equivalent Log4j2 configuration to the conso

[jira] [Updated] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1517: - Description: Add {{Add ThreadContext.setContext(Map)}}. Note that we have {{ThreadContext.setSta

[jira] [Updated] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1516: - Description: Add API {{ThreadContextMap.putAll(Map)}}. My immediate goal is to be able to build

[jira] [Updated] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1516: - Description: Add API {{ThreadContextMap.putAll(Map)}}. My immediate goal is to be able to build

[jira] [Updated] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1517: - Description: Add {{Add ThreadContext.setContext(Map)}}. My immediate goal is to be able to build

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421219#comment-15421219 ] Gary Gregory commented on LOG4J2-1447: -- It seems like the "get" and "put" APIs shoul

[jira] [Commented] (LOG4J2-1447) Garbage-free data structure for LogEvent's context map data

[ https://issues.apache.org/jira/browse/LOG4J2-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421215#comment-15421215 ] Gary Gregory commented on LOG4J2-1447: -- The proposed interface {{ContextData}} sure

[jira] [Updated] (LOG4J2-1517) Add ThreadContext.setContext(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1517: - Description: Add {{Add ThreadContext.setContext(Map)}}. My immediate goal is to be able to build

[jira] [Updated] (LOG4J2-1508) Allow a Builder to subclass another Builder

[ https://issues.apache.org/jira/browse/LOG4J2-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1508: - Summary: Allow a Builder to subclass another Builder (was: Allow a Builder to sublcass another B

[jira] [Updated] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1516: - Description: Add API {{ThreadContextMap.putAll(Map)}}. My immediate goal is to be able to build

[jira] [Updated] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1516: - Description: Add API {{ThreadContextMap.putAll(Map)}}. My immediate goal is to be able to build

[jira] [Updated] (LOG4J2-1516) Add ThreadContextMap.putAll(Map)

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1516: - Description: Add API {{ThreadContextMap.putAll(Map)}}. My immediate goal is to be able to build

[jira] [Updated] (LOG4J2-1518) Deadlock when using pure async and toString logs another message

[ https://issues.apache.org/jira/browse/LOG4J2-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leon Finker updated LOG4J2-1518: Attachment: 10511.jstack Full thread dump attached. I can see that the async logger processor threa

Re: Migrating from Log4j 1

I support reopening it. It seems to be a common feature request/complaint for 2.x for upgrading. On 15 August 2016 at 05:55, Remko Popma wrote: > I would be okay with that, but I'd like to print out a warning message and > the equivalent Log4j2 configuration to the console without any option to

Re: Migrating from Log4j 1

I would be okay with that, but I'd like to print out a warning message and the equivalent Log4j2 configuration to the console without any option to switch this off. Sent from my iPhone > On 2016/08/15, at 17:48, Mikael Ståldal wrote: > > Any objections to reopening LOG4J2-63, and targeting i

Re: Migrating from Log4j 1

Any objections to reopening LOG4J2-63, and targeting it for 2.7? On Sat, Aug 13, 2016 at 1:18 PM, Mikael Ståldal wrote: > Seems to be in https://issues.apache.org/jira/browse/LOG4J2-63 > > It is currently marked as Won’t Fix. Should we reopen this issue? > > On Aug 13, 2016 1:04 PM, "Mikael Stål