Re: Problem on including DTD entity in a log4j configuration file
Hi Curt The message is reporting that the content after common.xml is merged is not valid according to the DTD. The DOMConfigurator is less strict than the DTD that specifies (ignoring atypical elements) all the appender elements appear first, then any logger elements, then an optional root element. In XML DTD, if you cannot constrain the number of elements of a specific type without constraining the order. You are rigth that's the problem... Thanks - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
AUTO: Sandro Ruch/namics/com is out of the office. (returning 30.11.2009)
I am out of the office until 30.11.2009. I will respond to your message when I return. Note: This is an automated response to your message "Re: Problem on including DTD entity in a log4j configuration file" sent on 16.11.2009 02:48:04. This is the only notification you will receive while this person is away.
Re: bizarre NPE exception
Curt Arnold wrote: > Any chance that you are running this under Tomcat and this is occurring > after a reset? Tomcat had an issue with clearing out private static > members of classes but still leaving them in a callable state. glassfish v2 just what was bundled with Netbeans 6.7.1 on Linux 32/ubuntu It typically occurs after a while, or when I load up a new WAR file as I do the edit/compile/deploy/debug cycle -- Pat Farrell http://www.pfarrell.com/ - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: bizarre NPE exception
Curt Arnold wrote: > The log4j 1.2 date and date caching code is problematic and was replaced > in the abandoned log4j 1.3 effort which was then back-ported in the > EnhancedPatternLayout in the extras companion. If you goal is just to > side step the issues, then I would recommend using the > EnhancedPatternLayout. Yes, my goal is to see all log messages that make sense, and not see bugs within log4j itself. I think this is "yes" to your question. What's an EnhancedPatternLayout? how do I use it? Pointer to documentation that I've missed? I admit that my understanding of the log4j.properties is pretty weak, I usually just cut and paste from examples until it works. Pat -- Pat Farrell http://www.pfarrell.com/ - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: bizarre NPE exception
Any chance that you are running this under Tomcat and this is occurring after a reset? Tomcat had an issue with clearing out private static members of classes but still leaving them in a callable state. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: bizarre NPE exception
The log4j 1.2 date and date caching code is problematic and was replaced in the abandoned log4j 1.3 effort which was then back-ported in the EnhancedPatternLayout in the extras companion. If you goal is just to side step the issues, then I would recommend using the EnhancedPatternLayout. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: Problem on including DTD entity in a log4j configuration file
On Nov 15, 2009, at 2:25 PM, Brett Randall wrote: What is in common.xml, and is it valid according to the dtd? Brett The message is reporting that the content after common.xml is merged is not valid according to the DTD. The DOMConfigurator is less strict than the DTD that specifies (ignoring atypical elements) all the appender elements appear first, then any logger elements, then an optional root element. In XML DTD, if you cannot constrain the number of elements of a specific type without constraining the order. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: Problem on including DTD entity in a log4j configuration file
What is in common.xml, and is it valid according to the dtd?
Brett
On 11/16/09, Francis ANDRE wrote:
> Hi log4j users
>
> With the following log4j configuration:
> --
>
>
> ]>
> debug='true'>
>
> &common;
>
>
> ---
> I got a XML parsing warning as line 9 column 23 which is exactly the
> column just after the
>
> Any idea??
>
>
> log4j:WARN Continuable parsing error 9 and column 23
> log4j:WARN The content of element type "log4j:configuration" must match
> "(renderer*,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)".
> log4j: reset attribute= "false".
> log4j: Threshold ="null".
> log4j: Desired logger sub-class: [iso.itu.osi.msap.MSAPLogger]
> log4j: Setting [responder.iso.itu.osi.msap] additivity to [true].
> log4j: Level value for responder.iso.itu.osi.msap is [debug].
> log4j: responder.iso.itu.osi.msap level set to DEBUG
> log4j: Class name: [org.apache.log4j.FileAppender]
> log4j: Setting property [file] to [log/server.msap.log].
> log4j: Setting property [append] to [true].
> log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
> log4j: Setting property [conversionPattern] to [%d{ISO8601}: %-9p %5c{1}
> - %m
> ].
> log4j: setFile called: log/server.msap.log, true
> log4j: setFile ended
> log4j: Adding appender named [responder.msap.log] to category
> [responder.iso.itu.osi.msap].
> log4j: Desired logger sub-class: [iso.itu.osi.msap.MSAPLogger]
> log4j: Setting [initiator.iso.itu.osi.msap] additivity to [true].
> log4j: Level value for initiator.iso.itu.osi.msap is [debug].
> log4j: initiator.iso.itu.osi.msap level set to DEBUG
> log4j: Class name: [org.apache.log4j.FileAppender]
> log4j: Setting property [file] to [log/client.msap.log].
> log4j: Setting property [append] to [true].
> log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
> log4j: Setting property [conversionPattern] to [%d{ISO8601}: %-9p %5c{1}
> - %m
> ].
> log4j: setFile called: log/client.msap.log, true
> log4j: setFile ended
> log4j: Adding appender named [initiator.msap.log] to category
> [initiator.iso.itu.osi.msap].
> log4j: Desired logger sub-class: [iso.itu.osi.sap.SAPLogger]
> log4j: Setting [responder.iso.itu.osi] additivity to [true].
> log4j: Desired logger sub-class: [iso.itu.osi.sap.SAPLogger]
> log4j: Setting [initiator.iso.itu.osi] additivity to [true].
> log4j: Desired logger sub-class: [iso.itu.osi.tsap.TSAPLogger]
>
>
>
>
> -
> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>
>
--
Sent from my mobile device
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
Problem on including DTD entity in a log4j configuration file
Hi log4j users
With the following log4j configuration:
--
]>
debug='true'>
&common;
---
I got a XML parsing warning as line 9 column 23 which is exactly the
column just after the
Any idea??
log4j:WARN Continuable parsing error 9 and column 23
log4j:WARN The content of element type "log4j:configuration" must match
"(renderer*,appender*,plugin*,(category|logger)*,root?,(categoryFactory|loggerFactory)?)".
log4j: reset attribute= "false".
log4j: Threshold ="null".
log4j: Desired logger sub-class: [iso.itu.osi.msap.MSAPLogger]
log4j: Setting [responder.iso.itu.osi.msap] additivity to [true].
log4j: Level value for responder.iso.itu.osi.msap is [debug].
log4j: responder.iso.itu.osi.msap level set to DEBUG
log4j: Class name: [org.apache.log4j.FileAppender]
log4j: Setting property [file] to [log/server.msap.log].
log4j: Setting property [append] to [true].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{ISO8601}: %-9p %5c{1}
- %m
].
log4j: setFile called: log/server.msap.log, true
log4j: setFile ended
log4j: Adding appender named [responder.msap.log] to category
[responder.iso.itu.osi.msap].
log4j: Desired logger sub-class: [iso.itu.osi.msap.MSAPLogger]
log4j: Setting [initiator.iso.itu.osi.msap] additivity to [true].
log4j: Level value for initiator.iso.itu.osi.msap is [debug].
log4j: initiator.iso.itu.osi.msap level set to DEBUG
log4j: Class name: [org.apache.log4j.FileAppender]
log4j: Setting property [file] to [log/client.msap.log].
log4j: Setting property [append] to [true].
log4j: Parsing layout of class: "org.apache.log4j.PatternLayout"
log4j: Setting property [conversionPattern] to [%d{ISO8601}: %-9p %5c{1}
- %m
].
log4j: setFile called: log/client.msap.log, true
log4j: setFile ended
log4j: Adding appender named [initiator.msap.log] to category
[initiator.iso.itu.osi.msap].
log4j: Desired logger sub-class: [iso.itu.osi.sap.SAPLogger]
log4j: Setting [responder.iso.itu.osi] additivity to [true].
log4j: Desired logger sub-class: [iso.itu.osi.sap.SAPLogger]
log4j: Setting [initiator.iso.itu.osi] additivity to [true].
log4j: Desired logger sub-class: [iso.itu.osi.tsap.TSAPLogger]
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
