Vinay Srivastav Kasarla created LOG4J2-580:
--
Summary: Log4j 2 on Weblogic server
Key: LOG4J2-580
URL: https://issues.apache.org/jira/browse/LOG4J2-580
Project: Log4j 2
Issue Type:
[
https://issues.apache.org/jira/browse/LOG4J2-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-580.
---
Resolution: Invalid
Log4j 2 on Weblogic server
--
Key:
[
https://issues.apache.org/jira/browse/LOG4J2-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13946333#comment-13946333
]
Gary Gregory commented on LOG4J2-580:
-
Jira is not a support forum, please post your
Yeah, sorry, I thought you were discussing the other streaming api.
Gary
Original message
From: Matt Sicker boa...@gmail.com
Date:03/24/2014 23:46 (GMT-05:00)
To: Log4J Developers List log4j-dev@logging.apache.org
Subject: Re: Would like to change a bit of the
Hi All:
Our server uses v1's org.apache.log4j.net.XMLSocketReceiver.
I do not see a v2 equivalent.
Thoughts?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Editionhttp://www.manning.com/bauer3/
JUnit in Action, Second Edition
I'm not convinced we need it, but it was put there to make Level as close to a
real enum as possible. Every enum provides that static method (by way of
extending Enum).
N
On Mar 25, 2014, at 7:28 AM, Gary Gregory wrote:
Why do we have this API in org.apache.logging.log4j.Level:
public
Why do we have this API in org.apache.logging.log4j.Level:
public static T extends EnumT T valueOf(ClassT enumType, String
name) {
return Enum.valueOf(enumType, name);
}
?
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second
AbstractConfigurationTest is a confusing name. It is not abstract and it is
not subclassed. Better name?
Gary
On Sun, Mar 23, 2014 at 9:19 PM, Matt Sicker boa...@gmail.com wrote:
Interesting. There's already an AbstractConfigurationTest that's an
abstract ConfigurationTest, but there's also
We need to add receivers to log4j2 :)
Dcott
On Mar 25, 2014 5:19 AM, Gary Gregory garydgreg...@gmail.com wrote:
Hi All:
Our server uses v1's org.apache.log4j.net.XMLSocketReceiver.
I do not see a v2 equivalent.
Thoughts?
Gary
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Well, some Javadocs would help.
Gary
On Tue, Mar 25, 2014 at 8:31 AM, Nick Williams
nicho...@nicholaswilliams.net wrote:
I'm not convinced we need it, but it was put there to make Level as close
to a real enum as possible. Every enum provides that static method (by way
of extending Enum).
[
https://issues.apache.org/jira/browse/LOG4J2-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-579:
Summary: Rework Level comparison APIs (was: Rename Level.lessOrEqual() to
isLessOrEqual())
[
https://issues.apache.org/jira/browse/LOG4J2-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reopened LOG4J2-579:
-
Reopening for further discussion.
Rework Level comparison APIs
[
https://issues.apache.org/jira/browse/LOG4J2-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-579:
Description:
Rename Level.lessOrEqual() to isLessOrEqual().
Propose new API names.
was:Rename
[
https://issues.apache.org/jira/browse/LOG4J2-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-579:
Attachment: log4j2-579.diff
Rework Level comparison APIs
[
https://issues.apache.org/jira/browse/LOG4J2-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13946631#comment-13946631
]
Gary Gregory commented on LOG4J2-579:
-
Please see {{log4j2-579.diff}} for a proposed
[
https://issues.apache.org/jira/browse/LOG4J2-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13946588#comment-13946588
]
Stefan Klaus commented on LOG4J2-346:
-
Is the Patch already committed to the trunk. I
Please see {{log4j2-579.diff}} for a proposed new API set (
https://issues.apache.org/jira/secure/attachment/12636707/log4j2-579.diff).
I removed the int APIs since it feels like it is leaking encapsulation: the
user should not care that ints are used internally.
Thank you
Gary
On Mon, Mar 24,
This looks fine to me. There is some leakage that needs to happen. The
intLevel() method returns the int value and that is used by Logger in core to
make the level evaluation as fast as possible.
Ralph
On Mar 25, 2014, at 7:51 AM, Gary Gregory garydgreg...@gmail.com wrote:
Please see
We have JMS receivers and a SocketServer. I would expect that the
XMLSocketReceiver is expecting log events in XML format? If so, it would seem
that extending SocketServer to do that wouldn’t be very hard.
Ralph
On Mar 25, 2014, at 6:51 AM, Scott Deboy scott.de...@gmail.com wrote:
We need
On Tue, Mar 25, 2014 at 11:26 AM, Ralph Goers ralph.go...@dslextreme.comwrote:
This looks fine to me. There is some leakage that needs to happen. The
intLevel() method returns the int value and that is used by Logger in core
to make the level evaluation as fast as possible.
Thank you for
No, i don’t think so.
On Mar 25, 2014, at 8:32 AM, Gary Gregory garydgreg...@gmail.com wrote:
On Tue, Mar 25, 2014 at 11:26 AM, Ralph Goers ralph.go...@dslextreme.com
wrote:
This looks fine to me. There is some leakage that needs to happen. The
intLevel() method returns the int value
On Tue, Mar 25, 2014 at 1:20 PM, Ralph Goers ralph.go...@dslextreme.comwrote:
No, i don’t think so.
OK, I've marked the issue as resolved then.
Gary
On Mar 25, 2014, at 8:32 AM, Gary Gregory garydgreg...@gmail.com wrote:
On Tue, Mar 25, 2014 at 11:26 AM, Ralph Goers
[
https://issues.apache.org/jira/browse/LOG4J2-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-579.
-
Resolution: Fixed
Rework Level comparison APIs
Well, the old AbstractConfigurationTest was deleted. I merged that with the
XMLConfigurationTest (and the JSON and YAML ones that extended the old
AbstractConfigurationTest) into a new test that uses the parameterized
runner instead (they all tested the same thing, just different config file
I've been reading up on Camel lately. Maybe we could adopt some conventions
from there?
On 25 March 2014 10:29, Ralph Goers ralph.go...@dslextreme.com wrote:
We have JMS receivers and a SocketServer. I would expect that the
XMLSocketReceiver is expecting log events in XML format? If so, it
On Tue, Mar 25, 2014 at 9:36 PM, Matt Sicker boa...@gmail.com wrote:
Well, the old AbstractConfigurationTest was deleted. I merged that with
the XMLConfigurationTest (and the JSON and YAML ones that extended the old
AbstractConfigurationTest) into a new test that uses the parameterized
runner
On Tue, Mar 25, 2014 at 9:38 PM, Matt Sicker boa...@gmail.com wrote:
I've been reading up on Camel lately. Maybe we could adopt some
conventions from there?
Please explain.
Gary
On 25 March 2014 10:29, Ralph Goers ralph.go...@dslextreme.com wrote:
We have JMS receivers and a
Not prefixed with Abstract at least. There's no need for an abstract test
class in this scenario as it is more efficiently dealt with using a
@Parameters method. See:
OK, I think Camel is higher level than our low-level net bits.
Gary
On Tue, Mar 25, 2014 at 10:20 PM, Matt Sicker boa...@gmail.com wrote:
Using routes, consumers, producers, processors, endpoints, etc. All
enterprise integration pattern sort of things. Somewhat similar to how
Flume works,
On Tue, Mar 25, 2014 at 10:24 PM, Matt Sicker boa...@gmail.com wrote:
Not prefixed with Abstract at least. There's no need for an abstract test
class in this scenario as it is more efficiently dealt with using a
@Parameters method. See:
[
https://issues.apache.org/jira/browse/LOG4J2-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Brouwer updated LOG4J2-547:
-
Attachment: log4j2-547-remove-streams.patch
Perhaps we can agree to at least remove the
I don't mean using it. I mean borrowing the patterns it uses
architecturally. Though I might be thinking a bit too high level here to be
really useful.
So basically, we've got Appenders, Filters, Layouts (and patterns),
StrLookups, and ContextSelectors. Using Camel/EIP vocab, that gives us
[
https://issues.apache.org/jira/browse/LOG4J2-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-497:
--
Assignee: Matt Sicker
Create Log4j config JUnit rule.
---
[
https://issues.apache.org/jira/browse/LOG4J2-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-498:
--
Assignee: Matt Sicker
Update unit tests to use Log4jConfig rule.
[
https://issues.apache.org/jira/browse/LOG4J2-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13947551#comment-13947551
]
Matt Sicker commented on LOG4J2-498:
I've updated one unit test so far as well as
35 matches
Mail list logo
