Lacking any responses, I'll chime in:
I didn't know log4cxx existed. The only Cxx code I write is Java+Native. With
that said, now that I know it exists, I will investigate using it in my native
code; I'm not sure.
I'd love to try to help some, but I simply don't have time right now. I'm in
On Tue, Apr 23, 2013 at 6:19 PM, Nick Williams
nicho...@nicholaswilliams.net wrote:
Lacking any responses, I'll chime in:
I didn't know log4cxx existed. The only Cxx code I write is Java+Native. With
that said, now that I know it exists, I will investigate using it in my
native code; I'm
Is it possible to use two root loggers, one to capture trace and one to
capture errors (or more generally, two different levels)? If so, can
someone please provide a simple config example? Thanks.
--
Peter J. DePasquale, Ph.D.
Department of Computer Science
The College of New Jersey
(e) depasqua
You cannot have two root loggers but you can have multiple appender-refs on
them. Each appender-ref can have its own log level so I believe you get the
same behavior that you are looking for.
Ralph
On Apr 23, 2013, at 12:37 PM, Peter DePasquale wrote:
Is it possible to use two root loggers,
Can you point me to an example in the documentation? I didn't see anything
like that in there, that I recall...
On Tue, Apr 23, 2013 at 6:28 PM, Ralph Goers ralph.go...@dslextreme.comwrote:
You cannot have two root loggers but you can have multiple appender-refs
on them. Each appender-ref
I don't think the docs have an example yet. This one worked for me:
?xml version=1.0 encoding=UTF-8?
configuration status=WARN
appenders
File name=InfoFile fileName=level-info.log
PatternLayout
pattern%d %-5p %c{1.} [%t] %m %ex%n/pattern
/PatternLayout
/File
File
Actually, in reconsidering your question the solution is going to be a bit
messy. I haven't tried it but you should be able to do:
root level=trace
appender-ref ref=debugLog
thresholdFilter level=info onMatch=DENY onMismatch=NEUTRAL/
thresholdFilter level=debug onMatch=ACCEPT on
Your trace file will also contain info and above. From Peter's question I
understood him to mean he only wants events at that level. We don't have a
filter that does that specifically so I used two threshold filters to do it.
Ralph
On Apr 23, 2013, at 5:42 PM, Remko Popma wrote:
I don't
I see. I understood Peter's question differently. Let's hope one of our answers
solves his problem! :-)
Sent from my iPhone
On 2013/04/24, at 9:46, Ralph Goers ralph.go...@dslextreme.com wrote:
Your trace file will also contain info and above. From Peter's question I
understood him to mean
I am having a very difficult time learning the configuration system and am
very frustrated by the documentation. I had hoped to learn the system well
enough to possibly contribute to the project with respect to a tutorial or
other documentation, but I've concluded that I can no longer spend so
The approach I did is documented (perhaps poorly) at
http://logging.apache.org/log4j/2.x/manual/configuration.html in the section
titled configuring filters. Adding the level to the appender-ref may not be
documented. That was missed when the feature was added.
Ralph
On Apr 23, 2013, at 5:50
I continue to struggle achieving basic logging results under my web app
under tomcat. It seemed to work months ago, but when I upgraded to the
latest beta logging failed.
I returned to examine my config and failed to solve the problem. I emailed
this list about this and I received no response.
Peter,
I understand your frustration.
Let me try to help.
I'm at work now, so please understand if I am unable to reply to your messages
immediately.
First, I tried to do what you did originally (in your March 25th post), which
is a root logger and a named logger, each having a different
Peter,
I don't have Tomcat installed but I was able to reproduce the problem in a
standalone test using your configuration.
There is a couple of things I found.
First, File appenders have these configuration settings by default:
bufferedIO=true and immediateFlush=false.
This means that
14 matches
Mail list logo
