Re: logging-log4j2 git commit: LOG4J2-1526 Possibility to set StatusLogger destination in ConfigurationBuilder

The naming is the same as already used in XML and JSON config files. I think it would be confusing if different config formats uses different names for the same thing. On Thu, Aug 18, 2016 at 6:54 AM, Gary Gregory wrote: > Or: > > status = ERROR > status.destination = err > > Gary > > On Wed, A

[jira] [Commented] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426264#comment-15426264 ] Remko Popma commented on LOG4J2-1526: - If this is an existing attribute, can we alias

[jira] [Reopened] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1526: - > Possibility to set StatusLogger destination in ConfigurationBuilder > -

[jira] [Commented] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426293#comment-15426293 ] Mikael Ståldal commented on LOG4J2-1526: I gave it the name "dest" in properties

[jira] [Commented] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426294#comment-15426294 ] Mikael Ståldal commented on LOG4J2-1526: I agree that the naming "dest" is not ve

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426298#comment-15426298 ] Mikael Ståldal commented on LOG4J2-1528: OK, link removed. I still think this co

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426303#comment-15426303 ] Mikael Ståldal commented on LOG4J2-1528: My impression is that XML is the "main"

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426305#comment-15426305 ] Mikael Ståldal commented on LOG4J2-1528: Comment from [~garydgregory]: {{String

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426308#comment-15426308 ] Mikael Ståldal commented on LOG4J2-1528: What about the other method {{void write

Re: Migrating from Log4j 1

Look at the last comment here: https://issues.apache.org/jira/browse/ZOOKEEPER-2342 and here: https://issues.apache.org/jira/browse/HADOOP-12956 "backward-compatibility with the Log4J 1 properties file format would be hugely beneficial for us." On Wed, Aug 17, 2016 at 9:40 AM, Mikael Ståldal wro

[jira] [Commented] (LOG4J2-1525) Convert Log4j 1 log4j.properties into equvivalent Log4j 2 config file

[ https://issues.apache.org/jira/browse/LOG4J2-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426315#comment-15426315 ] Mikael Ståldal commented on LOG4J2-1525: Can we take the discussion about layouts

[jira] [Commented] (LOG4J2-1522) Log4j 1 layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426374#comment-15426374 ] Mikael Ståldal commented on LOG4J2-1522: Yes, that works. Removed TTCCLayout and

[jira] [Updated] (LOG4J2-1522) Log4j 1 layouts

[ https://issues.apache.org/jira/browse/LOG4J2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal updated LOG4J2-1522: --- Description: Support all layouts in Log4j 1 to the extent possible an reasonable. * PatternL

[jira] [Created] (LOG4J2-1530) LogEvent.getContextStack() can return null

Mikael Ståldal created LOG4J2-1530: -- Summary: LogEvent.getContextStack() can return null Key: LOG4J2-1530 URL: https://issues.apache.org/jira/browse/LOG4J2-1530 Project: Log4j 2 Issue Type:

[jira] [Commented] (LOG4J2-1528) Serialize configuration into a log4j2.xml file

[ https://issues.apache.org/jira/browse/LOG4J2-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426515#comment-15426515 ] Remko Popma commented on LOG4J2-1528: - A method returning the current object as a str

[jira] [Resolved] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1526. - Resolution: Fixed Agreed that a separate ticket for aliasing the {{dest}} attribute is a better

[jira] [Closed] (LOG4J2-1526) Possibility to set StatusLogger destination in ConfigurationBuilder

[ https://issues.apache.org/jira/browse/LOG4J2-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikael Ståldal closed LOG4J2-1526. -- > Possibility to set StatusLogger destination in ConfigurationBuilder > ---

Re: logging-log4j2 git commit: LOG4J2-1526 Possibility to set StatusLogger destination in ConfigurationBuilder

On Aug 18, 2016 1:31 AM, "Mikael Ståldal" wrote: > > The naming is the same as already used in XML and JSON config files. I think it would be confusing if different config formats uses different names for the same thing. Ah, I was not aware of that. Gary > > > On Thu, Aug 18, 2016 at 6:54 AM, Ga

Re: Migrating from Log4j 1

Neither of those imply that the conversion has to be at runtime. My concern here is that any conversion is unlikely to be 100% compatible, so providing a tool that creates a new configuration that you can then use and modify seems like a better way to go. It is also pretty much what Logback does

[jira] [Comment Edited] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426737#comment-15426737 ] Luca Burgazzoli edited comment on LOG4J2-905 at 8/18/16 4:23 PM: ---

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426748#comment-15426748 ] Michael Gysel commented on LOG4J2-905: -- Hi I'm out of office until September 19th and

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426737#comment-15426737 ] Luca Burgazzoli commented on LOG4J2-905: Cam just tries to log the route definitio

[jira] [Comment Edited] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426737#comment-15426737 ] Luca Burgazzoli edited comment on LOG4J2-905 at 8/18/16 4:43 PM: ---

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426800#comment-15426800 ] Gary Gregory commented on LOG4J2-905: - Thinking out-loud: If we provide/document a way

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426860#comment-15426860 ] Ralph Goers commented on LOG4J2-905: IMO, the correct solution is to add an option to

[jira] [Comment Edited] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426860#comment-15426860 ] Ralph Goers edited comment on LOG4J2-905 at 8/18/16 5:39 PM: -

[jira] [Issue Comment Deleted] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-905: --- Comment: was deleted (was: Hi I'm out of office until September 19th and I will not respond to my emai

[jira] [Commented] (LOG4J2-1529) composite configurations do not merge attributes on logger nodes

[ https://issues.apache.org/jira/browse/LOG4J2-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426898#comment-15426898 ] Sridevi Narra commented on LOG4J2-1529: --- Seems like this line of code is missing fr

[jira] [Created] (LOG4J2-1531) Change attribute and component values from String to Object

Roger Kapsi created LOG4J2-1531: --- Summary: Change attribute and component values from String to Object Key: LOG4J2-1531 URL: https://issues.apache.org/jira/browse/LOG4J2-1531 Project: Log4j 2

[site] Legacy section

Hi All: I think the Legacy section of the site should link to all Log4j versions. 2c, Gary -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition

Re: [site] Legacy section

Why? Log4j 2.3 is significant as it is the last release to support Java 6 and Log4j 1.2 is, of course, the last (and only) link to log4j 1. If we link to all then we would have 20 links there and it wouldn’t be obvious that log4j 2.3 was the last to support Java 6. Ralph > On Aug 18, 2016, a

[jira] [Created] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

Gary Gregory created LOG4J2-1532: Summary: Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing Key: LOG4J2-1532 URL: https://issue

[jira] [Updated] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

[ https://issues.apache.org/jira/browse/LOG4J2-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-1532: - Attachment: logging-log4j2.patch Proposed patch. > Don't throw an NPE from > org.apache.logging

[jira] [Commented] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

[ https://issues.apache.org/jira/browse/LOG4J2-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427295#comment-15427295 ] Gary Gregory commented on LOG4J2-1532: -- Also, since no one uses the return value fro

[jira] [Comment Edited] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

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

[jira] [Comment Edited] (LOG4J2-1532) Don't throw an NPE from org.apache.logging.log4j.core.LoggerContext.setConfiguration(Configuration) when the configuration is missing

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

Re: [site] Legacy section

Hi, In support scenarios, I often need to point users to the docs for the version they happen to be using in order for them to configure logging just so, which is rarely going to be one we list under Legacy. I can't just say look at the Log4j web site and pray that the version you are using provi

[jira] [Created] (LOG4J2-1533) Update Kafka client from 0.10.0.0 to 0.10.0.1

Gary Gregory created LOG4J2-1533: Summary: Update Kafka client from 0.10.0.0 to 0.10.0.1 Key: LOG4J2-1533 URL: https://issues.apache.org/jira/browse/LOG4J2-1533 Project: Log4j 2 Issue Type: I

[jira] [Reopened] (LOG4J2-1533) Update Kafka client from 0.10.0.0 to 0.10.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory reopened LOG4J2-1533: -- > Update Kafka client from 0.10.0.0 to 0.10.0.1 > - > >

[jira] [Closed] (LOG4J2-1533) Update Kafka client from 0.10.0.0 to 0.10.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1533. Resolution: Fixed In Git master. > Update Kafka client from 0.10.0.0 to 0.10.0.1 > ---

[jira] [Closed] (LOG4J2-1533) Update Kafka client from 0.10.0.0 to 0.10.0.1

[ https://issues.apache.org/jira/browse/LOG4J2-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory closed LOG4J2-1533. Resolution: Fixed Fix Version/s: 2.7 > Update Kafka client from 0.10.0.0 to 0.10.0.1 > -

[jira] [Closed] (LOG4J2-1284) Make default MessageFactory configurable

[ https://issues.apache.org/jira/browse/LOG4J2-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1284. --- Resolution: Fixed Updated Extending Log4j page: added section for MessageFactory. Committed to maste

[jira] [Created] (LOG4J2-1534) Create alias 'statusDestination' for 'dest' attribute in Configuration

Remko Popma created LOG4J2-1534: --- Summary: Create alias 'statusDestination' for 'dest' attribute in Configuration Key: LOG4J2-1534 URL: https://issues.apache.org/jira/browse/LOG4J2-1534 Project: Log4j 2

[jira] [Commented] (LOG4J2-1510) why MutableLogEvent don't keep original log object or even the ReusableObjectMessage

[ https://issues.apache.org/jira/browse/LOG4J2-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427452#comment-15427452 ] Remko Popma commented on LOG4J2-1510: - [~maple.feng.w...@hotmail.com], You marked thi

[jira] [Commented] (LOG4J2-1457) Class loader deadlock when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427455#comment-15427455 ] Remko Popma commented on LOG4J2-1457: - If this has been addressed, can we mark it as

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427458#comment-15427458 ] Remko Popma commented on LOG4J2-1531: - Roger, would you mind providing a patch for th

[jira] [Updated] (LOG4J2-1534) Create alias 'statusDestination' for 'dest' attribute in Configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1534: Priority: Minor (was: Major) > Create alias 'statusDestination' for 'dest' attribute in Configurat

[jira] [Commented] (LOG4J2-1529) composite configurations do not merge attributes on logger nodes

[ https://issues.apache.org/jira/browse/LOG4J2-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427466#comment-15427466 ] Remko Popma commented on LOG4J2-1529: - [~narras], would you be able to provide a patc

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

[ https://issues.apache.org/jira/browse/LOG4J2-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reopened LOG4J2-1516: - Sorry for the delay in taking a look at this. The main problem I have with this is that {{ThreadCont

[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 ] Remko Popma closed LOG4J2-1519. --- Resolution: Fixed Closing again after taking a better look. I reopened LOG4J2-1516 instead. > Add Th

[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=15427480#comment-15427480 ] Remko Popma commented on LOG4J2-1517: - Do we still need {{ThreadContext.setContext(Ma

[jira] [Comment Edited] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427458#comment-15427458 ] Remko Popma edited comment on LOG4J2-1531 at 8/19/16 1:52 AM: -

[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=15427483#comment-15427483 ] Gary Gregory commented on LOG4J2-1517: -- IMO yes. > Add ThreadContext.setContext(Map

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427486#comment-15427486 ] Remko Popma commented on LOG4J2-905: I like this idea of having an option that disable

[jira] [Assigned] (LOG4J2-1527) NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's getFormattedMessage() is called.

[ https://issues.apache.org/jira/browse/LOG4J2-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma reassigned LOG4J2-1527: --- Assignee: Remko Popma > NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's

[jira] [Updated] (LOG4J2-1527) NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's getFormattedMessage() is called.

[ https://issues.apache.org/jira/browse/LOG4J2-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1527: Fix Version/s: 2.7 > NPE thrown when log4j2 used within a webapp and RingBufferLogEvent's > getFor

[jira] [Assigned] (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 ] Remko Popma reassigned LOG4J2-1518: --- Assignee: Remko Popma > Deadlock when using pure async and toString logs another message > -

[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=15427494#comment-15427494 ] Remko Popma commented on LOG4J2-1518: - By default the AsyncQueueFullPolicy will only

[jira] [Commented] (LOG4J2-1531) Change attribute and component values from String to Object

[ https://issues.apache.org/jira/browse/LOG4J2-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427496#comment-15427496 ] Roger Kapsi commented on LOG4J2-1531: - Certainly. > Change attribute and component v

[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=15427498#comment-15427498 ] Remko Popma commented on LOG4J2-1517: - But why? Users can do ThreadContext.clearMap()

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427524#comment-15427524 ] Gary Gregory commented on LOG4J2-905: - Agreed, that's cool. Then later we can think of

[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=15427527#comment-15427527 ] Gary Gregory commented on LOG4J2-1517: -- So that you can do it in one line instead of

Build failed in Jenkins: Log4j 2.x #2175

See Changes: [rpopma] Removed superfluous prefix [rpopma] Update docs for garbage-free message factory [rpopma] LOG4J2-1284 improve documentation for customizing MessageFactory -- [...truncated 251

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427544#comment-15427544 ] Gary Gregory commented on LOG4J2-905: - What happens if you say: {code:java} log.info(

[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: Environment: Solaris (was: Linux/WIndows/Solaris) > Deadlock when using pure async and toString lo

[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=15427578#comment-15427578 ] Leon Finker commented on LOG4J2-1518: - Yes on Solaris. But I thought that issue was a

[jira] [Commented] (LOG4J2-1284) Make default MessageFactory configurable

[ https://issues.apache.org/jira/browse/LOG4J2-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427579#comment-15427579 ] Fabien Baligand commented on LOG4J2-1284: - Nice! Thank you! > Make default Messa

[jira] [Comment Edited] (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=15427578#comment-15427578 ] Leon Finker edited comment on LOG4J2-1518 at 8/19/16 4:08 AM: -

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

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-1529) composite configurations do not merge attributes on logger nodes

[ https://issues.apache.org/jira/browse/LOG4J2-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427611#comment-15427611 ] Sridevi Narra commented on LOG4J2-1529: --- Yes. > composite configurations do not m

Re: logging-log4j2 git commit: Remove unused import.

Gary, Can you please fix your import static settings? +import static org.junit.Assert.assertEquals; +import static org.junit.Assert.assertFalse; +import static org.junit.Assert.assertNotNull; +import static org.junit.Assert.assertTrue; ... -import static org.junit.Assert.*; On Fri, Aug 19, 201

[jira] [Commented] (LOG4J2-905) Ability to disable (date) lookup completely, compatibility issues with other libraries like camel

[ https://issues.apache.org/jira/browse/LOG4J2-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427670#comment-15427670 ] Gary Gregory commented on LOG4J2-905: - I've isolated the behavior in a unit test: {{o