[
https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714654#comment-13714654
]
Remko Popma commented on LOG4J2-124:
Ralph, in LOG4J2-318 you mention that you don't b
Performance testing is an interesting subject and can be quite subtle.
I recommend using a micro-benchmark framework like Caliper or JMH for this, it
is very easy to make a mistake and end up measuring something other than what
you intended. I've made mistakes myself and I've read people much mor
I've performed some performance tests for the JDBC and JPA Appenders. The
results are interesting and somewhat confusing, so I wanted to share them. All
of these tests were run on Java 1.6.0_51 on a MacBook Pro 15" 2.5 GHz Intel
Core i7 8GB 1333 MHz DDR3 running Mac OS X 10.7.5.
The abstract te
I had not considered that "bridge" might suggest that the log4j-1.2 jar would
be needed. That's a good reason not to use "bridge" actually.
My reason for disliking "api" was that in the past when people asked which jars
to use I'd say "the api and the core jars", and that's why I didn't like hav
[
https://issues.apache.org/jira/browse/LOG4J2-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-165.
Resolution: Fixed
Fix Version/s: 2.0-beta9
slf4j-ext was made an optional dependency in revi
Ahh. I wasn't aware of that. I'll add future changes at the top.
Nick
On Jul 20, 2013, at 6:44 PM, Ralph Goers wrote:
> Oh - I was expecting to see them at the top since that is where new changes
> are generally added.
>
> Ralph
>
> On Jul 20, 2013, at 4:23 PM, Nick Williams wrote:
>
>> I di
Oh - I was expecting to see them at the top since that is where new changes are
generally added.
Ralph
On Jul 20, 2013, at 4:23 PM, Nick Williams wrote:
> I did update changes.xml. Not sure why you don't see it, but it's there:
>
> http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/ch
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714571#comment-13714571
]
Ralph Goers edited comment on LOG4J2-318 at 7/20/13 11:22 PM:
--
I did update changes.xml. Not sure why you don't see it, but it's there:
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/changes/changes.xml?r1=1505102&r2=1505209&diff_format=h
Nick
On Jul 20, 2013, at 6:21 PM, Ralph Goers wrote:
> I didn't see an update to changes.xml. Since this
I didn't see an update to changes.xml. Since this is a breaking change I would
definitely expect to see it in the list of changes.
Ralph
On Jul 20, 2013, at 2:58 PM, Nick Williams wrote:
> The conversion from
> "handleExceptions"/"suppressExceptions"/"isExceptionSuppressed" to
> "ignoreExcep
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-318.
Resolution: Fixed
Fix Version/s: 2.0-beta9
Add shutdownHook attribute to the configuration e
Why do you dislike including "api" in the name. I have a problem with "bridge"
because to me it implies that I also need the Log4j 1.2 jar. I prefer the
current name because it provides the Log4j 1.2 API (not the Log4j 1.2
implementation). The fact that it is part of Log4j 2.0 should make it
There are two conversations. The first is on ignore vs. suppress. The
second is on javadocing cleary what the chosen term means.
On Jul 20, 2013 5:42 PM, "Ralph Goers" wrote:
> Well - I saw "hold everything" and then that was followed by "we need
> proper documentation". So I got the impression
Well - I saw "hold everything" and then that was followed by "we need proper
documentation". So I got the impression this was going to be a documentation
change, not a code change (except, I suppose to fix the handleExceptions
variable). But you made the change and it isn't worth the trouble t
Well, first, my main intent for this whole thing was consistency. We have
consistency now.
In the message you reference, I said that I could see how ignoreExceptions
could also be somewhat confusing (due to the dictionary meaning of ignore), but
also said that no matter what we did it would nee
On Jul 20, 2013, at 16:19, Nick Williams
wrote:
Correction below:
On Jul 20, 2013, at 2:38 PM, Nick Williams wrote:
Finally got back to working on this. Noticed two things:
1) On some appenders, ignoreExceptions/suppressExceptions defaults to true.
On other ones it defaults to false. We should
I'm confused. With your message on the 18th I thought you had changed your
mind and agreed that "suppressExceptions" was a better choice than
"ignoreExceptions" since it more accurately describes what is being done.
Ralph
On Jul 20, 2013, at 2:58 PM, Nick Williams wrote:
> The conversion from
On Jul 20, 2013, at 15:39, Nick Williams
wrote:
Finally got back to working on this. Noticed two things:
1) On some appenders, ignoreExceptions/suppressExceptions defaults to true.
On other ones it defaults to false. We should be consistent in this, and
IMO it should default to true. Does anyone
On Jul 20, 2013, at 16:23, Ralph Goers wrote:
Logback always suppresses exceptions. I am not sure about Log4j 1.x without
looking at the code but it may suppress them as well. My first reaction is
to say that suppressing exceptions should be the default but I'd want to
know which Appenders are de
The conversion from
"handleExceptions"/"suppressExceptions"/"isExceptionSuppressed" to
"ignoreExceptions" has been completed.
I still have some work to do to make sure these are being used/abided by
consistently and to make sure that all appenders and managers really do let
exceptions propagat
Yeah - that seems to work.
Ralph
On Jul 20, 2013, at 1:35 PM, Nick Williams wrote:
> You left out the exclamation point.
>
> If value of "junk" is specified and the defaultValue is true then
> (!"false".equalsIgnoreCase("junk") && true) returns true.
>
> However, it should actually be (defaul
You left out the exclamation point.
If value of "junk" is specified and the defaultValue is true then
(!"false".equalsIgnoreCase("junk") && true) returns true.
However, it should actually be (defaultValue && !"false".equalsIgnoreCase(s))
so that it short-circuits it defaultValue is false.
Nick
Why does this not look right to me? If a value of "junk" is specified and the
defaultValue is true then ("false".equalsIgnoreCase("junk") && true) return
false, which is incorrect. It should just return the default value.
Ralph
On Jul 20, 2013, at 1:18 PM, Nick Williams wrote:
> Correction b
On Jul 20, 2013, at 3:22 PM, Ralph Goers wrote:
> Logback always suppresses exceptions. I am not sure about Log4j 1.x without
> looking at the code but it may suppress them as well. My first reaction is to
> say that suppressing exceptions should be the default but I'd want to know
> which App
Logback always suppresses exceptions. I am not sure about Log4j 1.x without
looking at the code but it may suppress them as well. My first reaction is to
say that suppressing exceptions should be the default but I'd want to know
which Appenders are defaulting to not suppress them.
Gary introduc
Correction below:
On Jul 20, 2013, at 2:38 PM, Nick Williams wrote:
> Finally got back to working on this. Noticed two things:
>
> 1) On some appenders, ignoreExceptions/suppressExceptions defaults to true.
> On other ones it defaults to false. We should be consistent in this, and IMO
> it sho
Finally got back to working on this. Noticed two things:
1) On some appenders, ignoreExceptions/suppressExceptions defaults to true. On
other ones it defaults to false. We should be consistent in this, and IMO it
should default to true. Does anyone have any objection to that?
2) o.a.l.l.core.he
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714523#comment-13714523
]
Ralph Goers commented on LOG4J2-318:
I am adding the configuration to allow disabling
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers reassigned LOG4J2-318:
--
Assignee: Ralph Goers
> On termination Log4j terminates before the application
> --
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714516#comment-13714516
]
Nick Williams commented on LOG4J2-318:
--
I can agree with that.
> On
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714460#comment-13714460
]
Gary Gregory commented on LOG4J2-318:
-
I think we should have a JMX subelement anyway.
[
https://issues.apache.org/jira/browse/LOG4J2-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams updated LOG4J2-242:
-
Assignee: Nick Williams
> Make Messages more fluent
> -
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714438#comment-13714438
]
Nick Williams commented on LOG4J2-318:
--
Agreed. It seems to me that we need the follo
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714438#comment-13714438
]
Nick Williams edited comment on LOG4J2-318 at 7/20/13 2:39 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714438#comment-13714438
]
Nick Williams edited comment on LOG4J2-318 at 7/20/13 2:39 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714437#comment-13714437
]
Nick Williams commented on LOG4J2-242:
--
I'd like to take a stab at this. I have some
Now THAT is definitely a Yahoo! problem. "FORGED_YAHOO_RCVD" means they
rejected your email because it's a Yahoo! email coming from a non-Yahoo! IP
address. Which means their systems aren't smart enough to ignore this rule for
emails sent from their users on their POP/IMAP services. Lovely.
I'm
Another gripe I have is that messages from my iPhone are often rejected:
Remote host said: 552 spam score (5.2) exceeded threshold
(FORGED_YAHOO_RCVD,HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_NONE,SPF_PASS
) [BODY]
Any idea how to fix this?
Sent from my iPhone
---
I realize I made a mistake: I would like to rename the log4j-1.2-api jar to
log4j-1.2-bridge-2.0.jar (without api in the name).
Emails have been very snappy for me. Perhaps your provider is marking some
as spam, or delaying some? Then again, you're using Yahoo! mail. I can't
encourage you enough to use someone else.
I will note: a lot of these messages used to be delivered to spam for me
(Gmail). So I created a filter "to:
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714431#comment-13714431
]
Remko Popma commented on LOG4J2-318:
I don't disagree with you.
If you want to implem
[
https://issues.apache.org/jira/browse/LOG4J2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714430#comment-13714430
]
Gary Gregory commented on LOG4J2-317:
-
I would just prepend {{RandomAccessFileAppender
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714429#comment-13714429
]
Gary Gregory commented on LOG4J2-318:
-
I do not like having to tweak the command line,
[
https://issues.apache.org/jira/browse/LOG4J2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714428#comment-13714428
]
Remko Popma commented on LOG4J2-317:
These make for some really wacky acronyms too: RA
[
https://issues.apache.org/jira/browse/LOG4J2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714426#comment-13714426
]
Remko Popma commented on LOG4J2-317:
Tricky to find a good name for the rolling versio
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714423#comment-13714423
]
Remko Popma commented on LOG4J2-318:
Or log4j2.disable.shutdownHook=true (because it's
[
https://issues.apache.org/jira/browse/LOG4J2-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714419#comment-13714419
]
Gary Gregory commented on LOG4J2-317:
-
I like {{RandomAccessFileAppender}}, it makes s
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714417#comment-13714417
]
Gary Gregory commented on LOG4J2-318:
-
You cannot control the order of JRE shutdown th
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714416#comment-13714416
]
Maurizio Sartori edited comment on LOG4J2-318 at 7/20/13 12:54 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714416#comment-13714416
]
Maurizio Sartori edited comment on LOG4J2-318 at 7/20/13 12:53 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maurizio Sartori updated LOG4J2-318:
Attachment: test.zip
Here is a test that shows the problem.
> On terminati
[
https://issues.apache.org/jira/browse/LOG4J2-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714415#comment-13714415
]
Gary Gregory commented on LOG4J2-242:
-
I do not see why not, just do not force a fluen
[
https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714413#comment-13714413
]
Gary Gregory commented on LOG4J2-124:
-
In Log4j 1.2, we have {{LogManager.shutdown()}}
Gary Gregory created LOG4J2-319:
---
Summary: Double stack trace logging with ANSI output
Key: LOG4J2-319
URL: https://issues.apache.org/jira/browse/LOG4J2-319
Project: Log4j 2
Issue Type: Bug
On Sat, Jul 20, 2013 at 2:48 AM, Remko Popma wrote:
> Gary,
>
> Would you mind creating a Jira ticket for this? With the volume of email
> on the list it drops off the horizon very quickly otherwise...
>
> Remko
>
>
Remko,
Sure, here you go: https://issues.apache.org/jira/browse/LOG4J2-319
Than
Maurizio Sartori created LOG4J2-318:
---
Summary: On termination Log4j terminates before the application
Key: LOG4J2-318
URL: https://issues.apache.org/jira/browse/LOG4J2-318
Project: Log4j 2
[
https://issues.apache.org/jira/browse/LOG4J2-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714375#comment-13714375
]
Remko Popma commented on LOG4J2-124:
Should we add a #shutdown() method to LogManager
[
https://issues.apache.org/jira/browse/LOG4J2-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714373#comment-13714373
]
Remko Popma commented on LOG4J2-303:
Tom, is this issue resolved?
> N
[
https://issues.apache.org/jira/browse/LOG4J2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-166.
Resolution: Fixed
Fix Version/s: 2.0-beta9
The problem was that when the default route was s
[
https://issues.apache.org/jira/browse/LOG4J2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-166:
---
Description:
I recently updated to using beta4 and ran into a problem upon startup where I
received
[
https://issues.apache.org/jira/browse/LOG4J2-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-166:
---
Description:
I recently updated to using beta4 and ran into a problem upon startup where I
received
[
https://issues.apache.org/jira/browse/LOG4J2-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714362#comment-13714362
]
Remko Popma commented on LOG4J2-242:
Nick, Ralph, Gary, is this in scope for the 2.0 G
[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714359#comment-13714359
]
Remko Popma commented on LOG4J2-10:
---
Timothy, we may not have the expertise in the Log4j
I don't have any problems, sorry :-|
On Sat, Jul 20, 2013 at 8:37 AM, Remko Popma wrote:
> Recently email from the Log4J Developers List has been acting strange: I
> receive messages out of order, sometimes many hours after they have been
> sent. I also see replies to emails that I never received
64 matches
Mail list logo
