If your examples included loggers I think it would show these added verbose
entries would be another logger at INFO but not a separate severity.
I think of levels in terms of relative numeric severity. DEBUG < INFO wrote:
> Hi All:
>
> I've just come across the need for distinguishing log entrie
+1
Checked the website, JavaDoc, LICENSE and NOTICE, hashes, built it
with mvn package and tested the dist artifact with Chainsaw, all look
good.
Thanks for your help Christian!
Scott
On 10/14/13, Christian Grobmeier wrote:
> Dear all,
>
> this is a vote for a new Apache Extras package.
>
> Ch
It's here:
https://logging.apache.org/log4j/extras/download.html
FYI, the main page links 'extras' to the above.
Looks like we need to nuke the other site..
On 10/20/13, Gary Gregory wrote:
> Hi All:
>
> I see the 1.1 site here:
> https://logging.apache.org/log4j/companions/extras/download.htm
Yes, it looks like something went a bit sideways with the -bin jar.
The source jar is correct (no Appender class), but the -bin jar does
have the additional classes in it.
Scott
On 10/20/13, Jess Holle wrote:
> So I just downloaded apache-log4j-extras-1.2.17-bin.zip, pulled out
> apache-log4j-ex
it
> its way into the -bin artifact.
> I will investigate this… any ideas on the error are welcome.
>
>
>
> On 20 Oct 2013, at 21:31, Scott Deboy wrote:
>
>> Yes, it looks like something went a bit sideways with the -bin jar.
>> The source jar is correct (no Appender
:45, Jess Holle wrote:
>
>> Do note that the Maven build includes all the duplicates -- I just
>> checked.
>>
>> Thus the issue is with the build configuration.
>>
>> On 10/20/2013 2:33 PM, Gary Gregory wrote:
>>> On Sun, Oct 20, 2013 at 3:31 PM, Scott Deboy
I think I fixed it in commit 1534007.
Extras is no longer a 'bundle'.
Scott
On 10/20/13, Christian Grobmeier wrote:
> On 20 Oct 2013, at 21:29, Gary Gregory wrote:
>
>> On Sun, Oct 20, 2013 at 3:26 PM, Scott Deboy
>> wrote:
>>
>>> It's here:
Gah I committed that on the tag..
sigh..
Sorry
On 10/20/13, Scott Deboy wrote:
> I think I fixed it in commit 1534007.
>
> Extras is no longer a 'bundle'.
>
> Scott
>
> On 10/20/13, Christian Grobmeier wrote:
>> On 20 Oct 2013, at 21:29, Gary Gregory wrote
Reverted...but I see we have -18-snapshot in the pom now..I'll just
remove the bundle packaging entry on trunk..Christian, would you mind
rolling a 1.2.17.1 RC?
Scott
On 10/20/13, Scott Deboy wrote:
> Gah I committed that on the tag..
>
> sigh..
>
> Sorry
>
> On 10
+1 Everything looks good to me.
On 10/26/13, Jess Holle wrote:
> Is anyone going to vote on 1.2.17.1?
>
> I'll use this release in any case, but it would be nice if this was the
> latest public release in general.
>
> On 10/21/2013 9:26 AM, Christian Grobmeier wrote:
>> On 21 Oct 2013, at 15:28,
I'm on Mac Mavericks, using:
java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
admin@spiff:~$
On 11/23/13, Gary Gregory wrote:
> On Sat, Nov 23, 2013 at 9:45 AM, Gary Gregory
> wrote:
>
>> O
I think it makes sense to go through the existing bugs and find ones we
feel are critical and squash them before a final 2.0.
Gary's right in the sense that adoption as a non beta means we will feel
resistance to significant changes.
Maybe we should make it clear that Api changes may appear in 2.
public to allow Appender implementations to be
>> written.
>>
>> Gary
>>
>> Gary
>>
>>
>> On Fri, Jan 3, 2014 at 12:19 AM, Scott Deboy
>> wrote:
>> I think it makes sense to go through the existing bugs and find ones we
>> feel are c
I'm ok with those new levels.
Scott
On Jan 17, 2014 8:51 PM, "Nick Williams"
wrote:
> Wanted to update y'all. As you know, I've been very absent lately due to
> the book consuming every minute of my free time. I know I haven't been
> contributing my due, and for that please accept my sincerest a
+1 for a minimal jar with the servlet support.
On Jan 18, 2014 9:36 AM, "Ralph Goers" wrote:
> I’ve always had reservations about the servlet 3.0 automatic configuration
> because if the log4j jar is present it can’t be disabled or be modified by
> the end user. We’ve had some issues with Spring
Expression filter from log4j 1 already supports all of this and hasn't had
to change for years. Markers could be supported as a property with almost
zero work.
On Jan 18, 2014 2:52 PM, "Gary Gregory" wrote:
> On Sat, Jan 18, 2014 at 5:26 PM, Ralph Goers
> wrote:
>
>> We could address that by all
That looks good. Without all the trace levels IMO.
Scott
On Jan 20, 2014 7:49 PM, "Gary Gregory" wrote:
> On Mon, Jan 20, 2014 at 10:40 PM, Paul Benedict wrote:
>
>> If you really want extra logging levels without the long debate, just go
>> copy the logging levels of Apache HTTPD. They already
Right, that's what I meant. One trace level.
On Jan 20, 2014 8:15 PM, "Gary Gregory" wrote:
> On Mon, Jan 20, 2014 at 11:08 PM, Scott Deboy wrote:
>
>> That looks good. Without all the trace levels IMO.
>>
>
> Well, we'd want to keep the ONE TRACE
See http://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender
On 1/21/14, Saibabu Vallurupalli wrote:
> First of all Thanks so much for you all for the quickest response for this
> posting. I am thinking of writing a wrapper class and update the source,
> but we have about 2400 Ja
This mechanism is also available in log4j 1.2:
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/rewrite/RewriteAppender.html
On 1/21/14, Scott Deboy wrote:
> See
> http://logging.apache.org/log4j/2.x/manual/appenders.html#RewriteAppender
>
> On 1/21/14, Saibabu Valluru
I don't think the two have to be mutually exclusive - we can enhance
'custom level' support via a new mechanism and add built-in support
for the new levels as well.
I personally don't think they're confusing, as folks have mentioned,
httpd uses them.
I used to think of levels as 'severities', but
k from preventing them. The intention behind this
> proposal was to get agreement by scuttling the new levels but allowing
> anyone to add them in their own private code.
>
>
> On Thu, Jan 23, 2014 at 11:39 AM, Gary Gregory
> wrote:
>
>> Well said Scott.
>>
>>
I don't think we need a vote on the new level code..there's no good
technical reason to ask it to be removed, and it is likely to be
useful to some group of folks.
I think we're doing a good job on the other thread bouncing ideas of
how to handle extensible levels, and that conversation should con
consensus.
>
> If we follow the Apache process, the first vote will be open for 72 hours
> (correct me if I'm wrong) anyway. That should give everyone enough time to
> explain their position on the new levels before we start the second vote.
> Who knows, perhaps we're all
Gary
>>
>>
>>>
>>> The fact that changes for these levels have already been committed is
>>> IMHO not an argument in its favor. On the contrary, I was surprised at
>>> the
>>> timing of this commit: it was clear that many people were o
erence between trace and debug is already
>>> difficult for a lot of users.
>>> In the past two years i asked a lot of people how they log.
>>>
>>> The answer was: exceptions on error, the rest on debug.
>>>
>>> What we lack is a good recommendatio
If levels are just a name and a value why require a class at all? What
about just having it defined in the configuration.
On Jan 25, 2014 4:37 PM, "Ralph Goers" wrote:
> Because we don't know the class name that the Level belongs to. It is
> referenced in the configuration just as "DIAG", not
>
> The class is needed because it is a name and a value (two items) that has
> to be represented as a single parameter to Logger methods. Using raw int
> or String is not a good alternative.
>
> Ralph
>
> On Jan 25, 2014, at 4:54 PM, Scott Deboy wrote:
>
> If levels are just
AM, Ralph Goers > > wrote:
>>
>>> I am not sure what you mean by this. I have already succeeded in adding
>>> custom level names to the configuration and making them be valid. I am
>>> just trying to clean it up a bit based on what Nick is suggesting.
>>>
>
They can already do the same thing with loggers right?
Scott
On Jan 25, 2014 10:19 PM, "Ralph Goers" wrote:
> A malicious app could do
>
> for (int i=0; i < 10; ++i) {
> new Level(“Level” + i, 1000 + i){};
> }
>
> Sure idiots can do lots of bad things but I don’t think Levels should be
> q
So I assume we could build on this by adding the ability to generate these
custom levels from the config, with no user provided class required?
On Jan 26, 2014 12:58 AM, "Ralph Goers" wrote:
>
> I have completed the work on custom levels. It uses a variation of
Nick’s “extensible enum” class.
an 26, 2014 7:28 AM, "Scott Deboy" wrote:
> So I assume we could build on this by adding the ability to generate these
> custom levels from the config, with no user provided class required?
>
>
> On Jan 26, 2014 12:58 AM, "Ralph Goers"
> wrote:
> >
> &g
rectly do that. However, custom levels need to
> be mapped to the standard levels in several places. It would be simple to
> add support for that wherever you want it. Level.StdLevel.getStdLevel() is
> the method used to do that.
>
> Ralph
>
> On Jan 26, 2014, at 7:45 AM, Scott Deb
> configuration as well. I suppose that would entail adding a new
> element, with sub-elements like ...
> Is that what you are thinking of?
>
> I would be fine with that too, but would like to first focus on generating
> the extended Logger interface.
>
>
>
> On Mon
er that extends the default
> implementation, cache that implementation so that it doesn't have to be
> implemented again, and then instantiate/cache the logger instance like
> normal.
>
> Make sense?
>
> N
>
> On Jan 26, 2014, at 5:32 PM, Scott Deboy wrote:
>
>
be declared as a static
> from somewhere and it can only be instantiated a single time, so creating
> it from the configuration will prevent that.
>
> Ralph
>
> On Jan 26, 2014, at 4:03 PM, Scott Deboy wrote:
>
> I have one goal: to remove my request for new built in levels
If there is a way to support this strictly through configuration that would
be ideal.
I'm trying to find a way to remove my request for additional built in
levels but through configuration instead of adding them ourselves.
Scott
Scott
On Jan 26, 2014 7:38 PM, "Nick Williams"
wrote:
> Here's a s
, "hello world");
>>
>> work without actually creating SomeClass then please share!
>>
>> Ralph
>>
>> On Jan 26, 2014, at 7:45 PM, Nick Williams
>> wrote:
>>
>>> It would not be possible to do this strictly through configuration
>&g
;>> On Fri, Jan 24, 2014 at 2:38 PM, Gary Gregory >>> >wrote:
>>>>
>>>> There have been descriptions of what the levels are for... see Ralph '
>>>> message, many of mine and others. I know it can be tedious to go back
>>>> throu
please forgive brief replies and frequent typos
>
>> On Jan 26, 2014, at 22:37, Scott Deboy wrote:
>>
>> Yes, I would like to declare in the config:
>>
>> Level: NOTICE, value: 232
>>
>> And in Java code be able to use logger.notice("some message&
Of course, they'd have to use rhino, or something else...which doesn't
help. Where's duck typing when you need it :)
On 1/26/14, Scott Deboy wrote:
> Could we leverage Rhino? :)
>
> Scott
>
> On 1/26/14, Nicholas Williams wrote:
>> Scott, invokedynamic an
That way, this interface exists at compile time.
>
> On Monday, January 27, 2014, Nicholas Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>> Scott, invokedynamic and javassist...those are all /runtime/ things. The
>> user needs Logger#notice to be available at compile
Add setlevel. I also think appender belongs in Api. Yes?
On Jan 31, 2014 10:01 AM, "Gary Gregory" wrote:
> Porting from v1...
>
> We do not have Logger setLevel(Level) because it is not in the LCD API
> (Slf4j no, Logback yes, JUL yes).
>
> This sure makes it a pain to port from v1.
>
> What are
Re: appenders, I was thinking about Remko's response here:
http://stackoverflow.com/questions/21303746/migrating-from-log4j-1-2-to-log4j-2-how-to-get-list-of-all-appenders-and-rolli
On 1/31/14, Gary Gregory wrote:
> On Fri, Jan 31, 2014 at 1:05 PM, Scott Deboy wrote:
>
>> Add
uchbase 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 Grobmeier" wrote:
>
>> On 7 Feb 2014, at 16:19, Nick Will
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
+1 to couchbase
On Feb 7, 2014 7:54 AM, "Christian Grobmeier" 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 for MongoDB.
I'll check it out..apologies!
On 2/11/14, Remko Popma wrote:
> Gentle reminder: we need one more PMC vote to be able to release.
>
> On Tuesday, February 11, 2014, Christian Grobmeier
> wrote:
>
>> I think Rat is wrong on the jquery license.
>>
>> They have included a header, but its not identif
+1
(site looks good, tag built fine with mvn install, artifacts look good)
Scott
On 2/11/14, Scott Deboy wrote:
> I'll check it out..apologies!
>
> On 2/11/14, Remko Popma wrote:
>> Gentle reminder: we need one more PMC vote to be able to release.
>>
>&g
essed twice at startup.
>>>> o LOG4J2-398: Configure properties and setup Interpolator before
>>>> processing rest of configuration.
>>>> o LOG4J2-470: hostName property was not being set until after the
>>>> first
>>>> configuration element.
>>>>
Hi Ralph,
Glad to hear you're getting better!
Scott
On 2/21/14, Gary Gregory wrote:
> Ralph,
>
> It is great to hear that you are out of the hospital! Please do take care
> of yourself and don't overdo it ;) Log4J can wait... :)
>
> Gary
>
>
> On Fri, Feb 21, 2014 at 12:19 AM, Ralph Goers
> wro
Many of those already exist outside of Apache.
Scott
On Mar 14, 2014 2:29 PM, "Matt Sicker" wrote:
> I see we have log4j, log4net, log4php, and log4cxx. How about Python,
> Ruby, Perl, etc.? Anything incubating? Anyone interested in working on one?
>
> --
> Matt Sicker
>
We need to add receivers to log4j2 :)
Dcott
On Mar 25, 2014 5:19 AM, "Gary Gregory" 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
> Java Pers
Nope, it just shows my personal repositories, even though I am part of
the 'Apache' organization in GitHub.
On 4/14/14, Matt Sicker wrote:
> https://travis-ci.org/apache/logging-log4j2
>
> If you log in with your GitHub account, does it give you any administrative
> options? Particularly from the
And mine:
DBAHCIEFG
On 6/3/14, Ralph Goers wrote:
> In case it is not clear, the names (Aragorn, etc) below are for some other
> fictional vote to illustrate how to vote
>
> Here is my vote:
>
> DABIEFHGC
>
> Ralph
>
> On Jun 3, 2014, at 1:08 PM, Ralph Goers wrote:
>
>> It is time to select a
+1
On Jun 6, 2014 10:07 PM, "Matt Sicker" wrote:
> I like both logos, so I'm good with however you guys would like to go.
> Vote or not.
>
>
> On 6 June 2014 20:57, Remko Popma wrote:
>
>> Scott, Matt, what do you think?
>>
>>
>> On Sat, Jun 7, 2014 at 10:48 AM, Ralph Goers
>> wrote:
>>
>>> How
We shouldn't close feature requests as won't fix. Someone may come along
later and decide to implement it.
It's ok to say no one is planning on working on the feature, and remind the
submitter that patches are welcome.
Scott
Scott
On Jun 9, 2014 6:46 AM, "Paul Benedict" wrote:
> I remember a t
I'd suggest trying the latest developer snapshot of Chainsaw, available at
http://people.apache.org/~sdeboy
Scott
On Jun 11, 2014 8:56 AM, "Arthur Hsieh (JIRA)" wrote:
>
> [
> https://issues.apache.org/jira/browse/LOG4J2-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpa
+1
On Jun 15, 2014 4:05 PM, "Ralph Goers" wrote:
> Do we need the builders? As I said, I prefer only one way for creating
> plugins.
>
> Ralph
>
> On Jun 15, 2014, at 2:49 PM, Remko Popma wrote:
>
> I see. I agree that the original format is much nicer.
>
> Matt, do you think you can achieve th
+1
On 6/26/14, Gary Gregory wrote:
> Or you could not run tests in parallel and keep it simple. This is not a
> problem that needs solving and make the code harder to understand and
> maintain.
>
> Gary
>
>
> On Thu, Jun 26, 2014 at 4:50 PM, Matt Sicker wrote:
>
>> A neat improvement to the port
+1
On Aug 5, 2014 7:18 AM, "Matt Sicker" wrote:
> This topic was brought up elsewhere, so I'd like to propose a vote on
> switching to Git.
>
> +1 for me
>
> --
> Matt Sicker
>
Chainsaw is actually the immediate need for the code signing cert.
Scott
On Aug 29, 2014 9:19 PM, "Ralph Goers" wrote:
> Why can’t it be used to sign release artifacts?
>
> Ralph
>
> On Aug 29, 2014, at 7:55 PM, Matt Sicker wrote:
>
> Oh that's definitely a different signing key. That's suppos
I believe what you want you can do now by defining an expression:
prop.User ~= 'gmc' || prop.User ~= 'user2'
See the tutorial available from the Help menu for details on expression (or
right-click in the 'refine focus on' or 'search' fields, or the color
settings expression box..
Let me know if
Hi Jim,
Thanks for the patch - it looks good - I'll apply it.
Scott
On Fri, Oct 26, 2012 at 6:10 AM, Mayer, Jim wrote:
> Hi,
>
> I've been using a recent trunk version of chainsaw to look at log files
> created with log4j's org.apache.log4j.xml.XMLLayout layout. I noticed that
> when I config
FYII did a similar (reverse) thing so the default Android logging could
be slurped in to Chainsaw (with Android's single-letter severities)...so in
theory, you can still use Chainsaw to read log files with weird severity
names..
>From LogFilePatternReceiver sources:
/**
* If the log f
There is also the fact that it makes code conversion from log4j to log4j2
less painful by reusing the same call to get a logger.
Scott
On Nov 4, 2012 11:20 AM, "Gary Gregory" wrote:
> I'm wondering if such a "root" class would benefit being called "Log4J" or
> ""Log4J2".
>
> final Logger logger
I need to go through chainsaw, which requires going through extras. Would
prefer to do that while in beta, but I don't want to slow down the great
progress either.
On Jan 1, 2013 11:37 AM, "Ralph Goers" wrote:
> I took me longer than I wanted but I have finally fixed all the issues I
> wanted to
If you aren't already, I'd suggest trying the latest developer snapshot.
It has built-in support for generating a Chainsaw configuration from a
fileappender/conversionpattern:
- File, load Chainsaw configuration menu
- Use fileappender entries from a log4j config file (can be .properties or
.xml
Latest developer snapshot is available here:
http://people.apache.org/~sdeboy
On Thu, Jan 17, 2013 at 1:55 PM, Scott Deboy wrote:
> If you aren't already, I'd suggest trying the latest developer snapshot.
>
> It has built-in support for generating a Chainsaw configuration fr
nd have the appropriate configurations automatically loaded for
> each environment, depending upon which jnlp link one clicks.
>
> ** **
>
> Is that possible?
>
> ** **
>
> *From:* Scott Deboy [mailto:scott.de...@gmail.com]
> *Sent:* Thursday, January 17, 2013
ott
On Thu, Jan 17, 2013 at 4:39 PM, Stein, Jason
wrote:
> Scott, not sure that I follow you when you say, “pushed Chainsaw to your
> own web server.” Do you mean try to create my own JNLP file?
>
> ** **
>
> *From:* Scott Deboy [mailto:scott.de...@gmail.com]
> *Sent:*
Yogi over on the user list just posted a message saying the extras
companion was not available on any mirrors he tried - only via the archive
repository.
Any ideas how to fix that?
Thanks
Scott
If it isn't a deal breaker, I'd say keep Java 5 support..if that changes in
the future, it changes..at least folks would have a version of log4j2 that
worked on Java5.
Scott
On Tue, Feb 26, 2013 at 11:48 AM, Ralph Goers wrote:
> No - I am actually using the Java 6 compiler and it is allowing
>
I have been deferring to Ralph on my work for Log4j2-155 (adding
layout/advertisement support for appenders), and adding a patch to
Jira...which isn't technically necessary, so maybe that's a formalism that
isn't helpful in this case.
Any objections to me committing the work once I have a test to
I'm not quite sure how to categorize this plugin type (what to provide for
a type/elementType), so please provide a suggestion. It seems this is a
one-off.
On Fri, Mar 1, 2013 at 8:53 AM, Scott Deboy (JIRA) wrote:
>
> [
> https://issues.apache.org/jira/browse/L
After working through the 'left out to attempt to get around spam blocker'
plugin support, I noticed something that I think may be an issue.
I have a default/no-op 'left out' implementation:
@Plugin(name = "default", type = "Core", elementType = "left out",
printObject = false)
public class Defaul
yout as well. To be honest, it
> probably would be nicer if elementType could default to the type attribute,
> but that is not possible since default values on annotations must be
> constants.
> >
> > Ralph
> >
> >
> > On Mar 13, 2013, at 10:52 PM, Scott Deboy wrote:
&g
+1
On Wed, Apr 3, 2013 at 4:35 AM, Gary Gregory wrote:
> The fewer jars the better IMO.
>
> Gary
>
> On Apr 3, 2013, at 5:53, Remko Popma wrote:
>
> These all look doable.
>
> About Statistics from various components, @Ralph, anything in particular
> you'd like to see? (If not, it is pretty ea
I could imagine it could be handy to connect via JMX and retrieve the last
X number of warn/error/fatal events via JMX...sounds like a JMXAppender
though more than stats..
On Wed, Apr 3, 2013 at 9:38 AM, Ralph Goers wrote:
> Core should be fine. I just don't want to drag any dependencies into t
Should we tackle the plugin name conflict issue I filed?
On Sun, Apr 7, 2013 at 5:06 PM, Ralph Goers wrote:
> I have been applying all the Jira issues that have patches. I would like
> to start the beta5 release by the end of the week. Please let me know if
> there are any blockers for the rele
I can commit something.I'll look to see if the current unit test coverage
is sufficient or if something else needs to be added.
On Sun, Apr 7, 2013 at 5:58 PM, Ralph Goers wrote:
> Do you want to create the patch?
>
> Ralph
>
> On Apr 7, 2013, at 5:11 PM, Scott Deboy wrote:
I'd like to avoid what we had with log4j 1.x - the receivers/companions
mess. Whether or something belongs in core or not is a fuzzy judgment call
sometimes. If possible, I would like to see as much as possible included
in a single 'release' (that includes 'receivers/companions' if they ever
are
the same
> issue in Commoms VFS and we do not split out in a bunch of jars, nice and
> simple.
>
> Gary
>
> On Apr 12, 2013, at 12:38, Scott Deboy wrote:
>
> I'd like to avoid what we had with log4j 1.x - the receivers/companions
> mess. Whether or something belo
omething belongs in core is what dependencies it requires. The
> functionality it provides is secondary to me. My preference is for the
> Log4j API & core to have as few dependencies as possible.
>
> Ralph
>
>
>
> On Apr 12, 2013, at 9:38 AM, Scott Deboy wrote:
>
>
Hmm add a CouchBaseReceiver for Chainsaw?
On Fri, Apr 26, 2013 at 12:28 PM, Christian Grobmeier
wrote:
> Got this by Twitter:
> https://github.com/zooldk/log4j-couchbase
>
> Supports 1.x, but 2.x support is also planned.
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> -
Thanks for posting to the dev list!
I've commented on your stackoverflow post. There were a few issues.
- Stale docs (sorry)
- No support in Chainsaw V2 for Log4j2 socketappenders yet
- Chainsaw wasn't setting up a 'tailing' log file receiver
configuration for the advertised fileappender
Tho
Please note, the latest 'release' of Chainsaw doesn't support Log4j2,
only the developer snapshot available here:
http://people.apache.org/~sdeboy
On 5/10/13, Scott Deboy wrote:
> Thanks for posting to the dev list!
>
> I've commented on your stackoverflow p
sion the horizontal resizing (of the
> recievers pane and the pane on the other side) seems to be broken, it's not
> really a problem, just a heads up.
>
> --M@
>
> On Fri, May 10, 2013 at 11:48 AM, Scott Deboy
> wrote:
>
>> Thanks for posting to the dev list!
>&g
toggles it
> between Connected ant Not Connected, but I can't see any of the messages
> that should be streaming in. Giving the receiver a level doesn't seem to
> fix it either. Any idea what the problem is?
>
> Also it seems that one of the restarts has fixed the horizontal
d I can right click to tell it I'd like to
>> see trace, but that's all I can get it to do. Restarting the receiver
>> doesn't seem to do anything. Double clicking does nothing.
>>
>> --M@
>>
>> On Fri, May 10, 2013 at 2:07 PM, Scott Deboy
>
t;> in zero conf. Right now I'm using a complete copy and paste of the
>> >> config
>> >> file you put in SO.
>> >>
>> >> I do see a receiver listed, and I can right click to tell it I'd like
>> >> to
>> >> see t
t got it. Thank you so much!
>
> For my next trick I'll play with the format string to get the "Logger"
> column to populate correctly, but that's minor and probably not hard.
>
> --M@
>
> On Fri, May 10, 2013 at 2:24 PM, Scott Deboy wrote:
>
>>
Spaces should work fine around logger names, as long as there are no
spaces in your logger names!
Can you describe what you are seeing that's weird?
On 5/10/13, M@ wrote:
> I'm just using a pattern I copied from the docs ;-)
>
> --M@
>
> On Fri, May 10, 2013 at 2:
Time
> 2013-05-10 14:46:50,649 (ms delta: 0)
> Thread
> AWT-EventQueue-0
> Message
> 14:46:50.434 [MainLoop] TRACE com.mds.simulator.MdsSimComponentImpl - tick
> Marker
>
> Throwable
>
> The logger is showing in the message but the the logger field reports
> Unknown
>
&
Mind pasting in your Log4j appender configuration? I'd like to fix
whatever is tripping this up.
On 5/10/13, Scott Deboy wrote:
> If appendNonMatches=true in the (VFS)LogFilePatternReceiver and a line
> of text from the log file can't be parsed (the regexp fails for th
Great!
I need to add a wiki topic on this..
On 5/10/13, M@ wrote:
> The problem was an errant 'sg'
>
> should have been
>
>
> It's working like a charm now, thanks again for all your help.
>
> --M@
>
> On Fri, May 10, 2013 at 3:01 PM, Scott
Thanks, taken care of.
On 5/10/13, M@ wrote:
> I edited your SO answer to not contain that mistake, it's awaiting peer
> review, do you have the ability to approve it?
>
> --M@
>
> On Fri, May 10, 2013 at 3:40 PM, Scott Deboy wrote:
>
>> Great!
>>
I'd prefer if we leave the extra parens. IMO clarity trumps teachable
moments. Just disable the warning?
On May 13, 2013 8:26 AM, "Nick Williams"
wrote:
> It's not 100% harmless, but it is harmless as far as operation of the code.
>
> To understand how it could cause "harm", consider the situatio
s just going to be plain
>> dangerous.
>>
>> Ralph
>>
>>
>> On May 13, 2013, at 9:50 AM, Remko Popma wrote:
>>
>>> +1 on extra parens
>>> Teachable moments always seem to happen on Friday night when you really
>>> want to go home but it.
Extras sounds ok.
Scott
On May 15, 2013 4:01 AM, "Christian Grobmeier" wrote:
> Hi,
>
> we have had Apache Companions Extras. Now we don't have subcomponents.
> What is the new name now? Is it log4j extras or is it log4j
> companions?
>
> I am asking because we need a location for the website an
1 - 100 of 556 matches
Mail list logo
