[
https://issues.apache.org/jira/browse/LOG4J2-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-661.
--
Resolution: Not a Problem
Closing as "Not a problem" per user request.
> AsyncLogger with RollingFileA
[
https://issues.apache.org/jira/browse/LOG4J2-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040414#comment-14040414
]
Bobby commented on LOG4J2-661:
--
Hello, just like #662, i have found that the root problem lie
Thanks for the clarification.
I created LOG4J2-678 for the site/docs.
About the Atlassian link, if the link said "Atlassian Jira" it might be less
confusing. Still, the first link on that page is the one users are most likely
to click first so it should be to our issue tracker. I don't mind a
Remko Popma created LOG4J2-678:
--
Summary: Minor issues with Log4j2 web site/documentation
Key: LOG4J2-678
URL: https://issues.apache.org/jira/browse/LOG4J2-678
Project: Log4j 2
Issue Type: Bug
Understood. Thank you.
Sent from my iPhone
> On 2014/06/23, at 8:57, Matt Sicker wrote:
>
> NoSQL doesn't have the concept of commits and transactions. Plus,
> closeAndCommit() was just calling close() when non-null, so it was a simple
> change overall. :)
>
>
>> On 22 June 2014 18:33, Rem
NoSQL doesn't have the concept of commits and transactions. Plus,
closeAndCommit() was just calling close() when non-null, so it was a simple
change overall. :)
On 22 June 2014 18:33, Remko Popma wrote:
> (Away from PC)
> Is this.commitAndClose(); really the same as Closer.closeSilent?
>
> Clos
(Away from PC)
Is this.commitAndClose(); really the same as Closer.closeSilent?
Closer only closes and does not commit...
Sent from my iPhone
> On 2014/06/23, at 3:15, mattsic...@apache.org wrote:
>
> Author: mattsicker
> Date: Sun Jun 22 18:15:20 2014
> New Revision: 1604632
>
> URL: http://s
[
https://issues.apache.org/jira/browse/LOG4J2-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-676.
Resolution: Fixed
> Failed to write log event to CouchDB due to error: Connection pool shut down
>
[
https://issues.apache.org/jira/browse/LOG4J2-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040208#comment-14040208
]
Matt Sicker commented on LOG4J2-676:
I believe this should be fixed as of revision 160
Matt Sicker created LOG4J2-677:
--
Summary: Upgrade LightCouch to 0.1.x
Key: LOG4J2-677
URL: https://issues.apache.org/jira/browse/LOG4J2-677
Project: Log4j 2
Issue Type: Dependency upgrade
[
https://issues.apache.org/jira/browse/LOG4J2-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040200#comment-14040200
]
Matt Sicker commented on LOG4J2-676:
This could be related to LOG4J2-591.
> Failed to
Mistaken files added. Reverting.
-- Forwarded message --
From:
Date: 22 June 2014 12:51
Subject: svn commit: r1604622 - in /logging/log4j/log4j2/trunk/log4j-core:
./ src/main/java/org/apache/logging/log4j/core/appender/db/
src/main/java/org/apache/logging/log4j/core/config/plugins
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040180#comment-14040180
]
Matt Sicker commented on LOG4J2-673:
Maven plugins generally get a separate classpath
Definitely a +1 on the checkstyle comments thing. I've seen that before in
other projects.
On 22 June 2014 08:26, Remko Popma wrote:
> There are certainly a lot of checkstyle errors/warnings.
> I occasionally see Eclipse warning about an unused import or an unused
> private field, but checkstyl
I will see if we can exclude the IDE directory from RAT. I think we do want to
include them in the source distribution.
In general, the source artifact includes everything in the source tree. The
source zip should be buildable (in fact, that is one of the things we should be
testing in the rel
+1 Site looks good, tests all pass, artifacts look good.
Potential issue:
RAT warns that src/ide/eclipse/4.3.2/organize-imports.importorder does not
have a license.
I could be wrong, but I don't think this is a showstopper. This file is not
in any of our binary distribution artifacts (although i
[
https://issues.apache.org/jira/browse/LOG4J2-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040138#comment-14040138
]
Remko Popma commented on LOG4J2-625:
That is great to hear. Thanks for the confirmatio
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040137#comment-14040137
]
Mck SembWever commented on LOG4J2-673:
--
ahh… i see 2.0-rc2 has already been cut and t
[
https://issues.apache.org/jira/browse/LOG4J2-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040135#comment-14040135
]
Scott Harrington commented on LOG4J2-625:
-
If it helps, I have compiled 1604433 an
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: 0005-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch
> plugin preloading f
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: (was:
0004-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch)
> plugin
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: (was:
0003-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch)
> plugin
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mck SembWever updated LOG4J2-673:
-
Attachment: 0004-LOG4J2-673-plugin-preloading-fails-in-shaded-jar-fil.patch
Patch updated.
I'm c
[
https://issues.apache.org/jira/browse/LOG4J2-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040130#comment-14040130
]
Mck SembWever edited comment on LOG4J2-673 at 6/22/14 1:35 PM:
-
There are certainly a lot of checkstyle errors/warnings.
I occasionally see Eclipse warning about an unused import or an unused
private field, but checkstyle seems a lot stricter...
I'll try to spend some time cleaning this up after rc2 is out.
I noticed that we occasionally break the checkstyle
[
https://issues.apache.org/jira/browse/LOG4J2-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040098#comment-14040098
]
Abid commented on LOG4J2-461:
-
It can be looked up in Oracle Support site as:
Bug 18998060 :
[
https://issues.apache.org/jira/browse/LOG4J2-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
P_W999 updated LOG4J2-676:
--
Description:
I'm trying to setup a NoSQL logger using Apache CouchDB. After logging a single
message, the logg
P_W999 created LOG4J2-676:
-
Summary: Failed to write log event to CouchDB due to error:
Connection pool shut down
Key: LOG4J2-676
URL: https://issues.apache.org/jira/browse/LOG4J2-676
Project: Log4j 2
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
29 matches
Mail list logo
