[jira] [Closed] (LOG4J2-2190) Output Json object for ObjectMessage in JsonLayout

[Franz Wong (JIRA)]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Franz Wong closed LOG4J2-2190.
--

Pull request is merged. Close issue

> Output Json object for ObjectMessage in JsonLayout
> --
>
> Key: LOG4J2-2190
> URL: https://issues.apache.org/jira/browse/LOG4J2-2190
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Franz Wong
>Assignee: Mikael Ståldal
>Priority: Major
> Fix For: 2.11
>
>
> Currently, the message field is a JSON "string" instead of a JSON object. We 
> should add a new parameter in JsonLayout to allow converting to JSON object 
> if it is ObjectMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (LOG4J2-2202) MarkerFilter onMismatch invalid attribute in .properties

[Kilian (JIRA)]

Kilian created LOG4J2-2202:
--

 Summary: MarkerFilter onMismatch invalid attribute in .properties
 Key: LOG4J2-2202
 URL: https://issues.apache.org/jira/browse/LOG4J2-2202
 Project: Log4j 2
  Issue Type: Bug
  Components: Filters
Affects Versions: 2.10.0
Reporter: Kilian


Trying to use the following configuration results in an error indicating that 
onMismatch is not a property of markerfilter while the docs state that this 
attribute exists.

[https://logging.apache.org/log4j/2.x/manual/filters.html#MarkerFilter]

{{filter.muteHeartbeatEvent.type = MarkerFilter}}
 {{filter.muteHeartbeatEvent.marker ="Heartbeat_Event"}}
 {{filter.muteHeartbeatEvent.onMatch = DENY}}
 {{filter.muteHeartbeatEvent.onMismatch = NEUTRAL}}

 {quote} 2018-01-20 11:11:51,881 main ERROR MarkerFilter contains an invalid 
element or attribute "onMismatch"
{quote}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2186) Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2

[Ralph Goers (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333274#comment-16333274
 ] 

Ralph Goers commented on LOG4J2-2186:
-

Yes. I looked at the connection pooling stuff Gary added but it legitimately 
looks like a core feature that is used by lots of plugins. However, many of the 
plugins that use it should be extracted from core.

> Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 
> 2
> ---
>
> Key: LOG4J2-2186
> URL: https://issues.apache.org/jira/browse/LOG4J2-2186
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Gary Gregory
>Assignee: Gary Gregory
>Priority: Major
> Fix For: 2.11
>
>
> Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2186) Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333268#comment-16333268
 ] 

Mikael Ståldal commented on LOG4J2-2186:


[~ralph.go...@dslextreme.com] I guess you should also consider vetoing adding 
new classes to log4j-core, unless they really have to be there and 
cannot be placed in another module.

> Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 
> 2
> ---
>
> Key: LOG4J2-2186
> URL: https://issues.apache.org/jira/browse/LOG4J2-2186
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Gary Gregory
>Assignee: Gary Gregory
>Priority: Major
> Fix For: 2.11
>
>
> Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (LOG4J2-2186) Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 2

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333268#comment-16333268
 ] 

Mikael Ståldal edited comment on LOG4J2-2186 at 1/20/18 5:36 PM:
-

[~ralph.go...@dslextreme.com] I guess you should also consider vetoing adding 
new classes to log4j-core, unless they really have to be there and cannot be 
placed in another module.


was (Author: mikaelstaldal):
[~ralph.go...@dslextreme.com] I guess you should also consider vetoing adding 
new classes to log4j-core, unless they really have to be there and 
cannot be placed in another module.

> Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP 
> 2
> ---
>
> Key: LOG4J2-2186
> URL: https://issues.apache.org/jira/browse/LOG4J2-2186
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Gary Gregory
>Assignee: Gary Gregory
>Priority: Major
> Fix For: 2.11
>
>
> Add a JDBC ConnectionSource that provides pooling through Apache Commons DBCP.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[Apache Jenkins Server]

See 

[jira] [Commented] (LOG4J2-2199) Move ProcessIdUtil out of log4j-api into log4j-core

[JIRA]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333225#comment-16333225
 ] 

Mikael Ståldal commented on LOG4J2-2199:


It will fix LOG4J2-2126 though.

> Move ProcessIdUtil out of log4j-api into log4j-core
> ---
>
> Key: LOG4J2-2199
> URL: https://issues.apache.org/jira/browse/LOG4J2-2199
> Project: Log4j 2
>  Issue Type: Task
>  Components: API, Core
>Affects Versions: 2.10.0
>Reporter: Remko Popma
>Priority: Major
>
> Now that there is a separate log4j-core-java9 and log4j-core is a 
> multi-release jar, we can move {{ProcessIdUtil}} out of log4j-api into 
> log4j-core.
> Hopefully this will fix LOG4J2-2038 and LOG4J2-2133.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (LOG4J2-2190) Output Json object for ObjectMessage in JsonLayout

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal updated LOG4J2-2190:
---
Fix Version/s: 2.11

> Output Json object for ObjectMessage in JsonLayout
> --
>
> Key: LOG4J2-2190
> URL: https://issues.apache.org/jira/browse/LOG4J2-2190
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Franz Wong
>Assignee: Mikael Ståldal
>Priority: Major
> Fix For: 2.11
>
>
> Currently, the message field is a JSON "string" instead of a JSON object. We 
> should add a new parameter in JsonLayout to allow converting to JSON object 
> if it is ObjectMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (LOG4J2-2190) Output Json object for ObjectMessage in JsonLayout

[JIRA]

 [ 
https://issues.apache.org/jira/browse/LOG4J2-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikael Ståldal resolved LOG4J2-2190.

Resolution: Fixed

In Git master, please verify and close.

> Output Json object for ObjectMessage in JsonLayout
> --
>
> Key: LOG4J2-2190
> URL: https://issues.apache.org/jira/browse/LOG4J2-2190
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Franz Wong
>Assignee: Mikael Ståldal
>Priority: Major
>
> Currently, the message field is a JSON "string" instead of a JSON object. We 
> should add a new parameter in JsonLayout to allow converting to JSON object 
> if it is ObjectMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2190) Output Json object for ObjectMessage in JsonLayout

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333218#comment-16333218
 ] 

ASF subversion and git services commented on LOG4J2-2190:
-

Commit bda0775a74e2b0138cde7538222d40e552d3d79a in logging-log4j2's branch 
refs/heads/master from [~franzilogy]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=bda0775 ]

LOG4J2-2190 add description of the 'objectMessageAsJsonObject' parameter


> Output Json object for ObjectMessage in JsonLayout
> --
>
> Key: LOG4J2-2190
> URL: https://issues.apache.org/jira/browse/LOG4J2-2190
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Franz Wong
>Assignee: Mikael Ståldal
>Priority: Major
> Fix For: 2.11
>
>
> Currently, the message field is a JSON "string" instead of a JSON object. We 
> should add a new parameter in JsonLayout to allow converting to JSON object 
> if it is ObjectMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2190) Output Json object for ObjectMessage in JsonLayout

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333219#comment-16333219
 ] 

ASF GitHub Bot commented on LOG4J2-2190:


Github user asfgit closed the pull request at:

https://github.com/apache/logging-log4j2/pull/141


> Output Json object for ObjectMessage in JsonLayout
> --
>
> Key: LOG4J2-2190
> URL: https://issues.apache.org/jira/browse/LOG4J2-2190
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Franz Wong
>Assignee: Mikael Ståldal
>Priority: Major
> Fix For: 2.11
>
>
> Currently, the message field is a JSON "string" instead of a JSON object. We 
> should add a new parameter in JsonLayout to allow converting to JSON object 
> if it is ObjectMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (LOG4J2-2190) Output Json object for ObjectMessage in JsonLayout

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333217#comment-16333217
 ] 

ASF subversion and git services commented on LOG4J2-2190:
-

Commit df6a3a33ae4975d337cd854d87605bf0db8453ac in logging-log4j2's branch 
refs/heads/master from [~franzilogy]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=df6a3a3 ]

LOG4J2-2190 support writing JSON object in message field


> Output Json object for ObjectMessage in JsonLayout
> --
>
> Key: LOG4J2-2190
> URL: https://issues.apache.org/jira/browse/LOG4J2-2190
> Project: Log4j 2
>  Issue Type: New Feature
>  Components: Core
>Reporter: Franz Wong
>Assignee: Mikael Ståldal
>Priority: Major
> Fix For: 2.11
>
>
> Currently, the message field is a JSON "string" instead of a JSON object. We 
> should add a new parameter in JsonLayout to allow converting to JSON object 
> if it is ObjectMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] logging-log4j2 pull request #141: LOG4J2-2190 support writing JSON object in...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/logging-log4j2/pull/141


---

[jira] [Commented] (LOG4J2-1883) Support precise timestamps (microsecond and nanosecond level)

[Remko Popma (JIRA)]

[ 
https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333182#comment-16333182
 ] 

Remko Popma commented on LOG4J2-1883:
-

I was about to push my branch when I got some hardware issue. I may be able to 
recover files, unsure. Anyway, it’ll take some time. 

> Support precise timestamps (microsecond and nanosecond level)
> -
>
> Key: LOG4J2-1883
> URL: https://issues.apache.org/jira/browse/LOG4J2-1883
> Project: Log4j 2
>  Issue Type: Bug
>  Components: Configurators
> Environment: Linux with any JDK including JDK1.8
>Reporter: Madhava Dass
>Assignee: Remko Popma
>Priority: Critical
>
> Used log4j and 'log4j2.xml' to configure timestamp format as:
> {code}
> 
> 
> 
> 
>  pattern="[%d{-MM-dd'T'HH:mm:ss.SSSXXX}{UTC}][%level][%logger{36}]:%msg%n"/>
> 
> 
> 
> 
> 
> 
> 
> 
> {code}
> This pattern produces the time stamp as:
> {code}
> [2017-03-29T13:55:28.363000][null]:[Thread-1]: - 
> {code}
> The desired output is:
> {code}
> [2017-03-29T13:55:28.363701-07:00][null]:[Thread-1]: - 
> {code}
> Different versions of JDKs were tried including JDK 1.8. It does not seem to 
> make any difference in the outcome.
> Is there a way to get the desired time stamp through pattern matching 
> configuration in the '*.xml' file?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)