Remko Popma created LOG4J2-530:
--
Summary: JMX Client GUI should dynamically update when
LoggerContext MBeans are registered/unregistered in MBean server
Key: LOG4J2-530
URL:
[
https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894151#comment-13894151
]
Remko Popma edited comment on LOG4J2-500 at 2/7/14 9:11 AM:
[
https://issues.apache.org/jira/browse/LOG4J2-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894494#comment-13894494
]
James Pretorius commented on LOG4J2-511:
Thanks Remko
Referenced appenders on
Geoff Ballinger created LOG4J2-531:
--
Summary: Rolled logfiles overwritten by RollingFile appender with
composite time and size based policies
Key: LOG4J2-531
URL: https://issues.apache.org/jira/browse/LOG4J2-531
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-529:
---
Attachment: webapp2.war
webapp1.war
I've attached two webapps (webapp1.war and
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894570#comment-13894570
]
Remko Popma edited comment on LOG4J2-529 at 2/7/14 2:49 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-500.
Resolution: Fixed
Fix Version/s: 2.0-rc1
Unloading one webapp unloads JMX MBeans for all
[
https://issues.apache.org/jira/browse/LOG4J2-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-500.
--
Unloading one webapp unloads JMX MBeans for all webapps
Hi
one minor thing in ClouchDBProvider:
* The Apache CouchDB implementation of {@link NoSQLProvider}.
*/
@Plugin(name = CouchDb, category = Core, printObject = true)
public final class CouchDBProvider
The name of this plugin is CouchDb while the correct name of the
product
is CouchDB:
also the packagename is just couch, but it should better be couchdb.
The name couch is misleading imho
On 7 Feb 2014, at 16:11, Christian Grobmeier wrote:
Hi
one minor thing in ClouchDBProvider:
* The Apache CouchDB implementation of {@link NoSQLProvider}.
*/
@Plugin(name = CouchDb, category
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894616#comment-13894616
]
Nick Williams commented on LOG4J2-529:
--
Remko, here's your problem:
{code:xml}?xml
It doesn't so much matter because the XML element names are case insensitive,
but if we change the plugin name for CouchDB we should probably also change it
for MongoDB. There's a reason I did that, I just can't remember what it was...
I don't see any compelling reason to rename the package.
[
https://issues.apache.org/jira/browse/LOG4J2-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894638#comment-13894638
]
Remko Popma commented on LOG4J2-511:
James, if you verified that this solution works
On 7 Feb 2014, at 16:19, Nick Williams wrote:
It doesn't so much matter because the XML element names are case
insensitive, but if we change the plugin name for CouchDB we should
probably also change it for MongoDB. There's a reason I did that, I
just can't remember what it was...
I don't
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-529:
---
Attachment: (was: webapp1.war)
Log4j2 does not auto-initialize on webapp deploy or
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-529:
---
Attachment: webapp1.war
Nick, that is a good point. I tested again after updating web.xml with the
I do want to remind everyone that vetoes are only valid if they are backed
by a technical justification.
Scott
On Feb 7, 2014 8:07 AM, Nick Williams nicho...@nicholaswilliams.net
wrote:
I'm not convinced it really makes a difference, but it's better than
couchdb, so if the majority wants
I would appreciate if there wasn't even a threat of veto.
I would like to see folks ask questions and talk about concerns, and then
only mention a veto when there is no other recourse.
On Feb 7, 2014 8:14 AM, Nick Williams nicho...@nicholaswilliams.net
wrote:
Yep. I would've accompanied any
folks thats what i meant.
Couchbase is a different database than CouchDB. They share the same
roots,
but meanwhile have some differences.
My guess is one needs a second appender.
The one we have seems to work with couchdb, so the package should be
named couchdb.
If we want to support
Yep. I would've accompanied any veto with technical justification. Since I
can't come up with a technical justification for renaming it to couchbase, I
won't veto it. :-)
N
On Feb 7, 2014, at 10:09 AM, Scott Deboy wrote:
I do want to remind everyone that vetoes are only valid if they are
Ohhh okay. I misunderstood. H. Well I suppose in that case we really must
rename it, although I'm not super happy about it. But I'm convinced it's
necessary.
I guess we rename the couch package to couchdb.
Nick
On Feb 7, 2014, at 10:23 AM, Christian Grobmeier wrote:
folks thats what i
I'm not convinced it really makes a difference, but it's better than couchdb,
so if the majority wants couchbase it I won't veto it. Be sure to change the
test package name, too.
Nick
On Feb 7, 2014, at 10:03 AM, Scott Deboy wrote:
+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian
The couchdb package part name sounds like a clear match to CouchDB, the
product.
Gary
On Fri, Feb 7, 2014 at 11:55 AM, Nick Williams
nicho...@nicholaswilliams.net wrote:
Ohhh okay. I misunderstood. H. Well I suppose in that case we really
must rename it, although I'm not super happy
[
https://issues.apache.org/jira/browse/LOG4J2-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-530.
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed in revision 1565741.
JMX Client GUI should
[
https://issues.apache.org/jira/browse/LOG4J2-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-530.
--
JMX Client GUI should dynamically update when LoggerContext MBeans are
registered/unregistered in MBean
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894667#comment-13894667
]
Remko Popma edited comment on LOG4J2-529 at 2/7/14 5:53 PM:
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-529:
---
Attachment: (was: webapp1.war)
Log4j2 does not auto-initialize on webapp deploy or
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-529:
---
Attachment: webapp30-listener.war
webapp30.war
Log4j2 does not auto-initialize on
+1 to couchbase
On Feb 7, 2014 7:54 AM, Christian Grobmeier grobme...@gmail.com wrote:
On 7 Feb 2014, at 16:19, Nick Williams wrote:
It doesn't so much matter because the XML element names are case
insensitive, but if we change the plugin name for CouchDB we should
probably also change it
Any showstoppers left for anyone?
https://issues.apache.org/jira/browse/LOG4J2-529 is not great, but not sure
if it qualifies as a showstopper...
I'll see if I can find time to work on
https://issues.apache.org/jira/browse/LOG4J2-520 this weekend, but this is
not a showstopper IMHO. So I'd be
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894841#comment-13894841
]
Nick Williams commented on LOG4J2-529:
--
I still can't duplicate this. I downloaded
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894853#comment-13894853
]
Nick Williams commented on LOG4J2-529:
--
I just tried a different approach and it
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894877#comment-13894877
]
Remko Popma commented on LOG4J2-529:
Very strange... I'll try again tomorrow with
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13894889#comment-13894889
]
Nick Williams commented on LOG4J2-529:
--
Yes, {{webapp30.war}} won't work in Tomcat
Okay. Absent any other feedback, I'm going to remove the
DriverManagerConnectionSource.
N
On Feb 6, 2014, at 4:03 PM, Matt Sicker wrote:
It'd be cleaner to just remove it. Perhaps we could include in log4j-samples
a sort of rudimentary connection pool factory using dbcp?
On 5 February
Let me do the package rename from couch to couchdb.
I am just after it
On 7 Feb 2014, at 19:29, Remko Popma wrote:
Any showstoppers left for anyone?
https://issues.apache.org/jira/browse/LOG4J2-529 is not great, but not
sure
if it qualifies as a showstopper...
I'll see if I can find time
I think the next release should be an RC (or beta), not the GA. There are
just too many changes since beta-9 IMO.
Ideally, there should only be minor fixes from RC to GA.
Gary
On Fri, Feb 7, 2014 at 4:03 PM, Christian Grobmeier grobme...@gmail.comwrote:
Let me do the package rename from
It's ok for me to make an RC.
I would like to avoid the beta from a community perspective.
I also don't don't think that we are beta anymore and it would
be misleading for the community. In fact, having a RC would
show we are close before.
You are more the beta guy where I am usually more into
On Fri, Feb 7, 2014 at 4:15 PM, Christian Grobmeier grobme...@gmail.comwrote:
It's ok for me to make an RC.
I would like to avoid the beta from a community perspective.
I also don't don't think that we are beta anymore and it would
be misleading for the community. In fact, having a RC would
On 7 Feb 2014, at 22:25, Gary Gregory wrote:
On Fri, Feb 7, 2014 at 4:15 PM, Christian Grobmeier
grobme...@gmail.comwrote:
It's ok for me to make an RC.
I would like to avoid the beta from a community perspective.
I also don't don't think that we are beta anymore and it would
be misleading
I am sorry that I didn't express myself better. For some reason I
thought everybody would know about the couchdb/couchbase issue.
I have committed the change to svn.
Sorry that I don't know if I should have opened an issue for this or add
an entry to changes.xml, maybe one can remind me...
On Fri, Feb 7, 2014 at 4:41 PM, Christian Grobmeier grobme...@gmail.comwrote:
On 7 Feb 2014, at 22:25, Gary Gregory wrote:
On Fri, Feb 7, 2014 at 4:15 PM, Christian Grobmeier grobme...@gmail.com
wrote:
It's ok for me to make an RC.
I would like to avoid the beta from a community
[
https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams closed LOG4J2-422.
Closing because not an issue anymore.
DriverManager for JDBC Appender should have argument for
[
https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-422.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
This issue is fixed with r1565838. However,
[
https://issues.apache.org/jira/browse/LOG4J2-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-442:
Assignee: Nick Williams
Log4j2 Database insert problem in Websphere
[
https://issues.apache.org/jira/browse/LOG4J2-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-489:
Assignee: Nick Williams
Should JPADatabaseManager being using so many transactions?
[
https://issues.apache.org/jira/browse/LOG4J2-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-457:
Assignee: Nick Williams
JDBCAppender does not release JDBC connections to the connection
[
https://issues.apache.org/jira/browse/LOG4J2-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-438.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-407.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-442.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-489.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-457.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565858 and r1565878. The database
[
https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams reassigned LOG4J2-475:
Assignee: Nick Williams
MongoDBConnection is broken because it uses addDecodingHook
[
https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-475.
--
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565889. Based it off of Matt's
[
https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-444.
--
Resolution: Not A Problem
Assignee: Nick Williams
According to the [EclipseLink logging
Yes, I'm confused by this addition to. Why did we do this?
Nick
On Jan 30, 2014, at 12:24 AM, Gary Gregory wrote:
I'm slightly confused by this addition because it seems redundant with using
StringFormattedMessage and StringFormattedMessageFactory
Gary
--
E-Mail:
Yes, they might as well follow the same pattern. I was already working on the
MongoDB provider, so I went ahead and renamed the package. I also added items
to changes.xml for both renames. I think this closes this discussion.
Nick
On Feb 7, 2014, at 3:51 PM, Christian Grobmeier wrote:
I am
[
https://issues.apache.org/jira/browse/LOG4J2-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895409#comment-13895409
]
Michael Kloster commented on LOG4J2-407:
Great news! I am on vacation but will be
Let's roll 2.0-rc1 tonight. We've all basically agreed that there are no
showstoppers. I've fixed a whole bunch of appender-related bugs, and there's no
issue with the Servlet 3.0 auto-initialization. Can someone kick that off so
that we can have a vote this weekend and get this out there ASAP?
I think it has something to do with making it easier to port call sites
from:
System.out.println(...)
and
Console.printf(...)
I do not think reusing these API names in Logger is a good idea though.
I'd like to remove them.
Gary
On Fri, Feb 7, 2014 at 10:18 PM, Nick Williams
On Fri, Feb 7, 2014 at 10:25 PM, Nick Williams
nicho...@nicholaswilliams.net wrote:
Yes, they might as well follow the same pattern. I was already working on
the MongoDB provider, so I went ahead and renamed the package. I also added
items to changes.xml for both renames. I think this closes
You can roll an RC whenever you see fit, that's fine by me.
I think we'll have to focus on OSGi for RC2...
Gary
On Fri, Feb 7, 2014 at 10:31 PM, Nick Williams
nicho...@nicholaswilliams.net wrote:
Let's roll 2.0-rc1 tonight. We've all basically agreed that there are no
showstoppers. I've
I have no idea how to roll an RC ... or if I even can. Do I have the necessary
karma? I thought only PMC members could?
Nick
On Feb 7, 2014, at 10:53 PM, Gary Gregory wrote:
You can roll an RC whenever you see fit, that's fine by me.
I think we'll have to focus on OSGi for RC2...
Gary
Sadly, cutting releases is an overly complex and an error prone process.
I've not done it for Log4j but it will be a good exercise. Each project
usually has it's own BUILDING.txt or Wiki with more or less detailed
instructions, scripts, and so on. I've done it for Commons and
HttpComponenent, it's
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma closed LOG4J2-529.
--
Log4j2 does not auto-initialize on webapp deploy or auto-deinitialize on
undeploy
[
https://issues.apache.org/jira/browse/LOG4J2-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma resolved LOG4J2-529.
Resolution: Not A Problem
Fix Version/s: 2.0-rc1
I've confirmed that in Tomcat 7.0.50, the
If I remember correctly this was added on request of a user.
They did not want to set the StringFormatterMessageFactory when obtaining a
Logger because that would force them to use the printf format everywhere.
If I remember correctly the use case was that they wanted to use the
message {} with {}
Ralph documented the release procedure here:
http://wiki.apache.org/logging/Log4j2ReleaseGuide
On Sat, Feb 8, 2014 at 2:25 PM, Gary Gregory garydgreg...@gmail.com wrote:
Sadly, cutting releases is an overly complex and an error prone process.
I've not done it for Log4j but it will be a good
68 matches
Mail list logo
