On Jun 28, 2005, at 7:18 PM, Dave wrote:
I tried
I'm using 1.3.0alpha6 in WSAD
This gets rid of the statements below generated internally starting
with
DEBUG
I need to get rid of the log4j:INFO stuff
is there any way?
I was working on this yesterday to get the log4j 1.2 tests passin
At 01:18 AM 6/29/2005 +0100, you wrote:
>I tried
>
>
>
>
>I'm using 1.3.0alpha6 in WSAD
>
>This gets rid of the statements below generated internally starting with
>DEBUG
>I need to get rid of the log4j:INFO stuff
>
>is there any way?
>
Build from source. alpha6 is seriously old at this point.
You can't have elements in arbitrary order. Read the error message and it
should be obvious
>> > <>
>> > Log4j:ERROR Parsing error on line 82 and column 23
>> > Log4j:ERROR The content of element type "log4j:configuration" must match
>> > "
In your case (based on XML file below), al
At 03:28 PM 6/28/2005 -0500, you wrote:
> java.net.ConnectException: Connection refused: connect
>
>Get's thrown if there is no socket server to connect to. This is with log4j
>version 1.2.11 I don't think I experienced said behavior with 1.2.9
>
I think you should retry with 1.2.9. I'm using it
I tried
I'm using 1.3.0alpha6 in WSAD
This gets rid of the statements below generated internally starting with
DEBUG
I need to get rid of the log4j:INFO stuff
is there any way?
** configurationOptionStr=null
** End of LogManager static initializer
log4j:INFO Creating new logger [com.raythe
Yep, u can implements you own appender and in the doAppend method parse the
getThrowableSrcRep result.
-Mensaje original-
De: Javier Gonzalez [mailto:[EMAIL PROTECTED]
Enviado el: Martes, 28 de Junio de 2005 04:59 p.m.
Para: Log4J Users List
Asunto: Re: Logging the exception message but
Could this be done implementing a custom appender/layout instead of
extending Logger? (I'm trying hard as I can to avoid dealing with the
source code of the app itself, since it isn't mine ;)
On 6/28/05, Lenin David Lozano Argel <[EMAIL PROTECTED]> wrote:
> You have to implement your own logger an
Mmmm, didn't see any XML errors and the complaint was about the last line...
(is the use of "${jboss.server.home.dir}" allowed?)
Have you tried using "debug=true" and watching the output while initializing?
Or maybe commenting each top-level element in turn to see if you can
isolate the offendin
http://jakarta.apache.org/log4j/";
debug="false">
I didn't get it... try copy-pasting it in the message body.
On 6/28/05, Schuweiler, Joel J. <[EMAIL PROTECTED]> wrote:
> It was attached to the email, did it not go through?
>
> -Original Message-
> From: Javier Gonzalez [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 28, 2005 3:43 PM
> T
You have to implement your own logger and override the log(Priority, Object,
Throwable) method to parse the exception as you want.
-Mensaje original-
De: Javier Gonzalez [mailto:[EMAIL PROTECTED]
Enviado el: Martes, 28 de Junio de 2005 03:31 p.m.
Para: log4j-user@logging.apache.org
Asun
It was attached to the email, did it not go through?
-Original Message-
From: Javier Gonzalez [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 28, 2005 3:43 PM
To: Log4J Users List
Subject: Re: Error using NullAppender in
Ummm, could you post your log4j.xml so we can look at it and see if
Ummm, could you post your log4j.xml so we can look at it and see if we
can help you with your problem? ;)
On 6/28/05, Schuweiler, Joel J. <[EMAIL PROTECTED]> wrote:
>
>
> <>
> Log4j:ERROR Parsing error on line 82 and column 23
> Log4j:ERROR The content of element type "log4j:configuration" m
Title: Error using NullAppender in
<>
Log4j:ERROR Parsing error on line 82 and column 23
Log4j:ERROR The content of element type "log4j:configuration" must match "
Joel Schuweiler
Middleware
[EMAIL PROTECTED]
Tel: 8-7900
--
Is there a way to configure an appender to log the Exception message
but not the stack trace? To get something like:
ERROR: javax.xml.rpc.JAXRPCException: java.net.MalformedURLException
instead of:
ERROR: javax.xml.rpc.JAXRPCException: java.net.MalformedURLException
at org.apache.axis.client
java.net.ConnectException: Connection refused: connect
Get's thrown if there is no socket server to connect to. This is with log4j
version 1.2.11 I don't think I experienced said behavior with 1.2.9
-
To unsubscribe, e-mail: [E
On Tue, 28 Jun 2005, Dave Gomboc wrote:
[small correction]
> public boolean someRoutine() {
>
> log.trace("Entered.");
>
> [boolean result = ;]
>
log.trace("Exiting: result = |{}|.", result);
return result;
> };
>
> };
I have code to launch several independent processes, which then set up
socket connections with each other. I'd like to use log4j to acquire
execution trace information to assist me in finding bugs in that code.
I have a LoggingConfiguration() that I call at the start of each
independent process
On Mon, 27 Jun 2005, Schuweiler, Joel J. wrote:
| I'm aware of everything you have typed in this email. I am not aware of
| a good way to implement it. Nor does anyone else on this mailing list
| apparently.
_WHY_ can't you use the apparently proper way of doing it, which is to use
the logger
19 matches
Mail list logo
