You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Edward Zarecor <ez...@camail.harvard.edu> on 2002/02/13 00:08:55 UTC
migrating from 1.1.3 to 1.2beta
I'm trying to migrate some working code from log4j 1.1.3 to 1.2beta. The
source compiles fine, but I'm getting the following messages at
runtime. I've noted changes to the .dtd, e.g., that class is not required,
not implied. However, the dtd still allows category and appender tags
inside <log4j:configuration> tags. Does anyone know the source of these
errors? Any help will be greatly appreciated.
Ed.
log4j:ERROR Parsing error on line 11 and column -1
log4j:ERROR Element "log4j:configuration" does not allow "category" here.
log4j:ERROR Parsing error on line 16 and column -1
log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
log4j:ERROR Parsing error on line 24 and column -1
log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: migrating from 1.1.3 to 1.2beta
Posted by Edward Zarecor <ez...@camail.harvard.edu>.
Thanks for the quick response and sorry for overlooking the obvious. This,
of course, fixed the problem.
Ed.
At 07:33 PM 2/13/2002 +0100, you wrote:
>You are not respecting log4j.dtd. The errors have nothing to do with
>the log4j version. :-)
>
>You must declare appender elements, followed by category or logger
>elements, and the root element.
>
>HTH, Ceki
>
>At 09:32 13.02.2002 -0500, Edward Zarecor wrote:
>>I've attached a copy of the xml config file that is generating the
>>errors. It's still logging by the way. The only difference is the
>>errors are spit out to standard out when I change which jar I'm point
>>to. Thanks for any help.
>>
>>Ed.
>>
>>
>>At 12:17 AM 2/13/2002 +0100, you wrote:
>>>Edward,
>>>
>>>Could you please provide the XML configuration file? It would make it easier
>>>to deal with the problem you are encountering. Thanks, Ceki
>>>
>>>At 18:08 12.02.2002 -0500, Edward Zarecor wrote:
>>>>I'm trying to migrate some working code from log4j 1.1.3 to
>>>>1.2beta. The source compiles fine, but I'm getting the following
>>>>messages at runtime. I've noted changes to the .dtd, e.g., that class
>>>>is not required, not implied. However, the dtd still allows category
>>>>and appender tags inside <log4j:configuration> tags. Does anyone know
>>>>the source of these errors? Any help will be greatly appreciated.
>>>>
>>>>Ed.
>>>>
>>>>log4j:ERROR Parsing error on line 11 and column -1
>>>>log4j:ERROR Element "log4j:configuration" does not allow "category" here.
>>>>log4j:ERROR Parsing error on line 16 and column -1
>>>>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>>>>log4j:ERROR Parsing error on line 24 and column -1
>>>>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>>>
>>>--
>>>Ceki Gülcü
>>>
>>>
>>>
>>>--
>>>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>>
>>
>>--
>>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>--
>Ceki Gülcü
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
SocketNode - Extended (II)
Posted by peter riegersperger <ri...@subnet.at>.
stupid mouse. always hits the "send" button before i'm done.
allright, again, but this time _with_ the attachment.
(this IS very embarrassing :P)
rick
|-
| peter riegersperger <ri...@subnet.at>
|-
| subnet
| platform for media art and experimental technologies
|-
| http://www.subnet.at/
|-
| muehlbacherhofweg 5 // 5020 salzburg // austria
|-
| fon/fax +43/662/842 897
|-
> -----Original Message-----
> From: peter riegersperger [mailto:rick@subnet.at]
> Sent: Wednesday, February 27, 2002 6:47 PM
> To: Log4J Users List
> Cc: ceki@qos.ch
> Subject: SocketNode - Extended
>
>
> mark suggested i should submit any changes i made to the SocketNode class.
> well, here it is.
>
> if you're wondering why the class needed changing:
> the original socketnode class does not have a method to close it. so, once
> you've started the thread for the socketnode, all you can do is kill the
> thread if you want to end or reset the process containing the thread (or
> multiple threads, depending on how many appenders are connected).
> using timeouts is not well suited for this situation, because if you shut
> down the logging server, you would want to stop all threads
> immediately, not
> after a certain period.
>
> since the class is very small, i decided to submit it to the list. inside
> the zip-file, you will also find the class LoggingServer, a very
> small class
> that starts a server listening for incoming connections on port 5000
> (hardcoded - see README for details) and spawning threads for
> socketappenders as they connect. (the server will also end the
> threads when
> it is told to)
>
> i hope that is useful for others.
>
> greetings,
>
> rick
>
> ps: every speech should end with acknowledgements thank-you's. i'd like to
> thank albert meixner for helping me with all these threading
> issues i still
> don't really understand.
>
>
>
> |-
> | peter riegersperger <ri...@subnet.at>
> |-
> | subnet
> | platform for media art and experimental technologies
> |-
> | http://www.subnet.at/
> |-
> | muehlbacherhofweg 5 // 5020 salzburg // austria
> |-
> | fon/fax +43/662/842 897
> |-
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
SocketNode - Extended
Posted by peter riegersperger <ri...@subnet.at>.
mark suggested i should submit any changes i made to the SocketNode class.
well, here it is.
if you're wondering why the class needed changing:
the original socketnode class does not have a method to close it. so, once
you've started the thread for the socketnode, all you can do is kill the
thread if you want to end or reset the process containing the thread (or
multiple threads, depending on how many appenders are connected).
using timeouts is not well suited for this situation, because if you shut
down the logging server, you would want to stop all threads immediately, not
after a certain period.
since the class is very small, i decided to submit it to the list. inside
the zip-file, you will also find the class LoggingServer, a very small class
that starts a server listening for incoming connections on port 5000
(hardcoded - see README for details) and spawning threads for
socketappenders as they connect. (the server will also end the threads when
it is told to)
i hope that is useful for others.
greetings,
rick
ps: every speech should end with acknowledgements thank-you's. i'd like to
thank albert meixner for helping me with all these threading issues i still
don't really understand.
|-
| peter riegersperger <ri...@subnet.at>
|-
| subnet
| platform for media art and experimental technologies
|-
| http://www.subnet.at/
|-
| muehlbacherhofweg 5 // 5020 salzburg // austria
|-
| fon/fax +43/662/842 897
|-
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: migrating from 1.1.3 to 1.2beta
Posted by Ceki Gülcü <ce...@qos.ch>.
You are not respecting log4j.dtd. The errors have nothing to do with
the log4j version. :-)
You must declare appender elements, followed by category or logger
elements, and the root element.
HTH, Ceki
At 09:32 13.02.2002 -0500, Edward Zarecor wrote:
>I've attached a copy of the xml config file that is generating the
>errors. It's still logging by the way. The only difference is the errors
>are spit out to standard out when I change which jar I'm point to. Thanks
>for any help.
>
>Ed.
>
>
>At 12:17 AM 2/13/2002 +0100, you wrote:
>>Edward,
>>
>>Could you please provide the XML configuration file? It would make it easier
>>to deal with the problem you are encountering. Thanks, Ceki
>>
>>At 18:08 12.02.2002 -0500, Edward Zarecor wrote:
>>>I'm trying to migrate some working code from log4j 1.1.3 to
>>>1.2beta. The source compiles fine, but I'm getting the following
>>>messages at runtime. I've noted changes to the .dtd, e.g., that class
>>>is not required, not implied. However, the dtd still allows category
>>>and appender tags inside <log4j:configuration> tags. Does anyone know
>>>the source of these errors? Any help will be greatly appreciated.
>>>
>>>Ed.
>>>
>>>log4j:ERROR Parsing error on line 11 and column -1
>>>log4j:ERROR Element "log4j:configuration" does not allow "category" here.
>>>log4j:ERROR Parsing error on line 16 and column -1
>>>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>>>log4j:ERROR Parsing error on line 24 and column -1
>>>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>>
>>--
>>Ceki Gülcü
>>
>>
>>
>>--
>>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Ceki Gülcü
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: migrating from 1.1.3 to 1.2beta
Posted by Edward Zarecor <ez...@camail.harvard.edu>.
I've attached a copy of the xml config file that is generating the
errors. It's still logging by the way. The only difference is the errors
are spit out to standard out when I change which jar I'm point to. Thanks
for any help.
Ed.
At 12:17 AM 2/13/2002 +0100, you wrote:
>Edward,
>
>Could you please provide the XML configuration file? It would make it easier
>to deal with the problem you are encountering. Thanks, Ceki
>
>At 18:08 12.02.2002 -0500, Edward Zarecor wrote:
>>I'm trying to migrate some working code from log4j 1.1.3 to 1.2beta. The
>>source compiles fine, but I'm getting the following messages at
>>runtime. I've noted changes to the .dtd, e.g., that class is not
>>required, not implied. However, the dtd still allows category and
>>appender tags inside <log4j:configuration> tags. Does anyone know the
>>source of these errors? Any help will be greatly appreciated.
>>
>>Ed.
>>
>>log4j:ERROR Parsing error on line 11 and column -1
>>log4j:ERROR Element "log4j:configuration" does not allow "category" here.
>>log4j:ERROR Parsing error on line 16 and column -1
>>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>>log4j:ERROR Parsing error on line 24 and column -1
>>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>
>--
>Ceki Gülcü
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: migrating from 1.1.3 to 1.2beta
Posted by Ceki Gülcü <ce...@qos.ch>.
Edward,
Could you please provide the XML configuration file? It would make it easier
to deal with the problem you are encountering. Thanks, Ceki
At 18:08 12.02.2002 -0500, Edward Zarecor wrote:
>I'm trying to migrate some working code from log4j 1.1.3 to 1.2beta. The
>source compiles fine, but I'm getting the following messages at
>runtime. I've noted changes to the .dtd, e.g., that class is not
>required, not implied. However, the dtd still allows category and
>appender tags inside <log4j:configuration> tags. Does anyone know the
>source of these errors? Any help will be greatly appreciated.
>
>Ed.
>
>log4j:ERROR Parsing error on line 11 and column -1
>log4j:ERROR Element "log4j:configuration" does not allow "category" here.
>log4j:ERROR Parsing error on line 16 and column -1
>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
>log4j:ERROR Parsing error on line 24 and column -1
>log4j:ERROR Element "log4j:configuration" does not allow "appender" here.
--
Ceki Gülcü
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>