[
https://issues.apache.org/jira/browse/LOG4J2-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1962.
Resolution: Fixed
Fix Version/s: 2.9
In git master.
> Update Apache Kafka client from 0.10.
On Tue, Jul 25, 2017 at 3:33 AM, Dominik Psenner wrote:
> If xx&&yy&&zz is complicated why not ship a makefile with an install target?
>
> On 25 Jul 2017 9:16 a.m., "Thorsten Schöning" wrote:
>
>> Guten Tag Robert Middleton,
>> am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie:
>>
>> > As far as
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/93
Hi @ta924 Any news?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
Github user garydgregory commented on the issue:
https://github.com/apache/logging-log4j2/pull/59
@mikaelstaldal Yes, this can be closed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
[
https://issues.apache.org/jira/browse/LOG4J2-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100979#comment-16100979
]
ASF subversion and git services commented on LOG4J2-1986:
-
Commit
I created a branch called LOG4J2-1986-b with what I think is a cleaner
implementation.
Gary
On Tue, Jul 25, 2017 at 7:40 AM, Matt Sicker wrote:
> The caller will get an unexpected unchecked exception in the alternative
> scenario as well.
>
> Anyways, it might not be a terrible idea to use chec
[
https://issues.apache.org/jira/browse/LOG4J2-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100977#comment-16100977
]
ASF subversion and git services commented on LOG4J2-1986:
-
Commit
Hey Mikael,
sorry for the slow response time.
GMail thought that - of all the dev mailing list mails - this specific mail
looked like spam. I just found it hidden in the spam folder...
The API looks good to me, assuming that I’ll be fine with the default c’tor
versions of Log4jJsonObjectMapper,
[
https://issues.apache.org/jira/browse/LOG4J2-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-1977.
Resolution: Fixed
Fix Version/s: 2.9
In Git master.
> Consider the StringBuilder's capacity
Github user asfgit closed the pull request at:
https://github.com/apache/logging-log4j2/pull/92
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
[
https://issues.apache.org/jira/browse/LOG4J2-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100624#comment-16100624
]
ASF subversion and git services commented on LOG4J2-1977:
-
Commit
[
https://issues.apache.org/jira/browse/LOG4J2-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Felder closed LOG4J2-1987.
--
> Log4J JUL Bridge and RMI Security Manager causes access denied
> ("java.util.logging.LoggingPerm
[
https://issues.apache.org/jira/browse/LOG4J2-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100129#comment-16100129
]
Andreas Felder commented on LOG4J2-1987:
This patch seems to work for me. At leas
The caller will get an unexpected unchecked exception in the alternative
scenario as well.
Anyways, it might not be a terrible idea to use checked exceptions deriving
from IOException in this API.
On 25 July 2017 at 02:49, Mikael Ståldal wrote:
> Right, but this one will not:
>
> public Log
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099987#comment-16099987
]
Remko Popma commented on LOG4J2-1988:
-
It would be better if we can verify that the {
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099955#comment-16099955
]
Corneliu C commented on LOG4J2-1988:
Hi,
this property has not been explicitly setup
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099926#comment-16099926
]
Remko Popma edited comment on LOG4J2-1988 at 7/25/17 12:15 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099926#comment-16099926
]
Remko Popma edited comment on LOG4J2-1988 at 7/25/17 12:00 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099926#comment-16099926
]
Remko Popma commented on LOG4J2-1988:
-
AsyncLoggerConfig should be taking a snapshot
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma reassigned LOG4J2-1988:
---
Assignee: Remko Popma
> java.util.ConcurrentModificationException with AsyncLogger?
> --
[
https://issues.apache.org/jira/browse/LOG4J2-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Corneliu C updated LOG4J2-1988:
---
Description:
Hi,
I see java.util.ConcurrentModificationException even with AsyncLogger and I
don't
Corneliu C created LOG4J2-1988:
--
Summary: java.util.ConcurrentModificationException with
AsyncLogger?
Key: LOG4J2-1988
URL: https://issues.apache.org/jira/browse/LOG4J2-1988
Project: Log4j 2
Is
Github user liyuj commented on the issue:
https://github.com/apache/logging-log4j2/pull/82
committing each time is very affecting performance.
The practice now is to commit once per minute, commit too often, will lead
to performance degradation, the submission interval is too long,
[
https://issues.apache.org/jira/browse/LOG4J2-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Lembeck closed LOG4J2-1982.
-
Fix is verified. Thanks a lot!
> Log4j-config.xsd only allows one AppenderRef element for ea
Jörn Huxhorn, would the API in Git branch LOG4J2-1986 work for you?
On 2017-07-22 22:49, Mikael Ståldal wrote:
Work in progress in Git branch LOG4J2-1986.
On 2017-07-22 22:31, Mikael Ståldal wrote:
Yes, I am putting it in its own Java package.
On 2017-07-22 22:13, Gary Gregory wrote:
Should
Right, but this one will not:
public LogEvent parseFrom(InputStream input) throws IOException,
ParseException {
return objectReader.readValue(input);
}
In any case I need to translate from Jackson's JsonProcessingException
to our ParseException.
On 2017-07-24
True, but the caller will get an unexpected checked exception in the face.
On 2017-07-25 00:19, Matt Sicker wrote:
rethrow(e) doesn't wrap the exception, so there's no useless exception.
On 24 July 2017 at 15:34, Mikael Ståldal wrote:
I could use "Throwables.rethrow(e)", but is that really
If xx&&yy&&zz is complicated why not ship a makefile with an install target?
On 25 Jul 2017 9:16 a.m., "Thorsten Schöning" wrote:
> Guten Tag Robert Middleton,
> am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie:
>
> > As far as I'm aware, the configure.sh is not platform-dependent,
>
> It is in
Guten Tag Robert Middleton,
am Dienstag, 25. Juli 2017 um 02:28 schrieben Sie:
> As far as I'm aware, the configure.sh is not platform-dependent,
It is in a sense that it's arbitrary old code generated on my platform
while obviously each other platform could generate better fitting one
on that pl
29 matches
Mail list logo
