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 peter riegersperger <ri...@subnet.at> on 2002/07/26 13:15:16 UTC
mdc & remote logging - DOH!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi all!
we are working on a distributed application (running on multiple
servers) that should facilitate a remote logging system.
that centralized logging should go into one logfile (since the
servers actions are highly dependend on each other), so i figured the
mdc would be the way to distinguish log entries from different
servers. smart? nope. the mdc of the logentries gets replaced by the
mdc from the logging server. if, for example, the remote server sets
MDC.put("hostname","host1"), and the logging server sets
MDC.put("hostname","loggingserver"), all entries from the remote
server are tagged with hostname=loggingserver.
after reading the javadoc, this behaviour sounds reasonable (since
the socketnode treats all incoming logging events as local).
i imagine that i'm not the only one developing for a distributed
system. so, how do you tackle the problem of tagging your log
messages?
any input welcome!
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
|-
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: public key available at http://home.subnet.at/rick/pgp/
iQA/AwUBPUEhNCDD9/SWDsvSEQLOHwCg7JUxXDHBLbBPWI5n9i6t9GxpeFsAoKHm
1iogyasNUPPdZixOxuPYZScc
=7+XE
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by peter riegersperger <ri...@subnet.at>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi ceki!
[snip from code]
> Does this help?
actually, no. (bear with me, please)
i did look up the code, but it seems to me that the logging server
should use its own mdc only if no mdc-copy is found, and the mdc-copy
should be created before the logging event is serialized.
so, i don't see why the logging server does use its own, and not the
copy.
what am i missing, or am i just plain stupid? (equal chances, i guess
:)
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
|-
>
> At 14:22 26.07.2002 +0200, you wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> > > See the source code for LoggingEvent.getMDC.
> >
> >sorry, i don't get it. the mdc is copied before serialization, but
> >the logging server still insists on putting its own in it?
> >
> >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
> >|-
> >
> >-----BEGIN PGP SIGNATURE-----
> >Version: PGPfreeware 6.5.8 for non-commercial use
> ><http://www.pgp.com> Comment: public key available at
> >http://home.subnet.at/rick/pgp/
> >
> >iQA/AwUBPUEw6CDD9/SWDsvSEQKNNQCeIjCNuaWEKXrSQEhgor9oeNgswBMAnjHi
> >a5zSBQoKlptS2wmW+jwcp/sE
> >=omBu
> >-----END PGP SIGNATURE-----
> >
> >
> >--
> >To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
>For additional commands, e-mail:
><ma...@jakarta.apache.org>
- --
Ceki
- --
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: public key available at http://home.subnet.at/rick/pgp/
iQA/AwUBPUE00yDD9/SWDsvSEQLWhACeIdaxOFGeZ+hwk08gKn0AmlnFS+kAnAuD
AfOC085xU1iDpW696fFpPlXb
=eWNu
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by Ceki Gülcü <ce...@qos.ch>.
/**
Returns the the context corresponding to the <code>key</code>
parameter. If there is a local MDC copy, possibly because we are
in a logging server or running inside AsyncAppender, then we
search for the key in MDC copy, if a value is found it is
returned. Otherwise, if the search in MDC copy returns a null
result, then the current thread's <code>MDC</code> is used.
<p>Note that <em>both</em> the local MDC copy and the current
thread's MDC are searched.
*/
public
Object getMDC(String key) {
Object r;
// Note the mdcCopy is used if it exists. Otherwise we use the MDC
// that is associated with the thread.
if(mdcCopy != null) {
r = mdcCopy.get(key);
if(r != null) {
return r;
}
}
return MDC.get(key);
}
Does this help?
At 14:22 26.07.2002 +0200, you wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
> > See the source code for LoggingEvent.getMDC.
>
>sorry, i don't get it. the mdc is copied before serialization, but
>the logging server still insists on putting its own in it?
>
>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
>|-
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
>Comment: public key available at http://home.subnet.at/rick/pgp/
>
>iQA/AwUBPUEw6CDD9/SWDsvSEQKNNQCeIjCNuaWEKXrSQEhgor9oeNgswBMAnjHi
>a5zSBQoKlptS2wmW+jwcp/sE
>=omBu
>-----END PGP SIGNATURE-----
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by peter riegersperger <ri...@subnet.at>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> See the source code for LoggingEvent.getMDC.
sorry, i don't get it. the mdc is copied before serialization, but
the logging server still insists on putting its own in it?
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
|-
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: public key available at http://home.subnet.at/rick/pgp/
iQA/AwUBPUEw6CDD9/SWDsvSEQKNNQCeIjCNuaWEKXrSQEhgor9oeNgswBMAnjHi
a5zSBQoKlptS2wmW+jwcp/sE
=omBu
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: mdc & remote logging - DOH!
Posted by Ceki Gülcü <ce...@qos.ch>.
See the source code for LoggingEvent.getMDC.
At 13:15 26.07.2002 +0200, peter riegersperger wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>hi all!
>
>we are working on a distributed application (running on multiple
>servers) that should facilitate a remote logging system.
>
>that centralized logging should go into one logfile (since the
>servers actions are highly dependend on each other), so i figured the
>mdc would be the way to distinguish log entries from different
>servers. smart? nope. the mdc of the logentries gets replaced by the
>mdc from the logging server. if, for example, the remote server sets
>MDC.put("hostname","host1"), and the logging server sets
>MDC.put("hostname","loggingserver"), all entries from the remote
>server are tagged with hostname=loggingserver.
>
>after reading the javadoc, this behaviour sounds reasonable (since
>the socketnode treats all incoming logging events as local).
>
>i imagine that i'm not the only one developing for a distributed
>system. so, how do you tackle the problem of tagging your log
>messages?
>
>any input welcome!
>
>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
>|-
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
>Comment: public key available at http://home.subnet.at/rick/pgp/
>
>iQA/AwUBPUEhNCDD9/SWDsvSEQLOHwCg7JUxXDHBLbBPWI5n9i6t9GxpeFsAoKHm
>1iogyasNUPPdZixOxuPYZScc
>=7+XE
>-----END PGP SIGNATURE-----
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by peter riegersperger <ri...@subnet.at>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ok, everybody get out your "i'm with stupid" - t-shirts ...
the logging application is using log4j-1.2.5, and the other
applications were using log4j-1.2beta2.
using 1.2.5 in the applications resolved the problem, and the mdc is
logged just fine.
thanks a lot,
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
|-
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: public key available at http://home.subnet.at/rick/pgp/
iQA/AwUBPUUGNCDD9/SWDsvSEQKfxwCfY8+qGVrld5P7Y03EfisYZRarhKcAn0ET
1rGkBumpPb2GxLA6iyHuEjSn
=Vilp
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by peter riegersperger <ri...@subnet.at>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> From: Ceki Gulcu [mailto:ceki@qos.ch]
> I have added several test cases to check whether there is a problem
> with the way the MDC is handled after serialization. I am happy to
> report that the existing code works as it should.
[...]
> I suggest that you write a small test case reproducing the problem.
as it turns out, log4j is handling everything fine in my testcase.
obviously, there is something broken in the code of our project (or
the setup). i can't check that because i'm at home, but i will report
back on monday. most likely it's some very embarrassing simple
mistake that i will have to cover up by some unintelligible mumbling
about somebody elses fault.
thanks a lot,
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
|-
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: public key available at http://home.subnet.at/rick/pgp/
iQA/AwUBPUJ94CDD9/SWDsvSEQKK1ACePwwPVIZD4qVq6Qi1PsfnxlT+qfEAoIah
U6Lxt5L2r2+sxE8MBLyBsLvu
=zL4y
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by Ceki Gülcü <ce...@qos.ch>.
I have added several test cases to check whether there is a problem
with the way the MDC is handled after serialization. I am happy to
report that the existing code works as it should.
Here are the remaining possibilities:
- You are mixing a client using log4j 1.1 with a server using log4j 1.2
- You are not setting the MDC key correctly
I suggest that you write a small test case reproducing the problem.
At 17:21 26.07.2002 +0200, peter riegersperger wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>hi!
>
> > What is the architecture? In the following text everything seems to
> > be a server, so it is not easy to understand your architecture nor
> > your question. Can you please clarify?
>
>sorry for not making myself clear.
>actually, our situation is quite simple. we have multiple
>applications running on multiple hosts. every application uses log4j
>and a SocketAppender connecting to our logging application.
>the logging application has SocketNodes in several threads running
>(one SocketNode for each connecting application). the logging
>application writes all entries (including its own logging statements)
>into a file.
>
>In the applications, we put some information into the MDC to identify
>the source of the log entry. but (as stated in my original mail), the
>MDC in the log entry from the application gets overwritten by the MDC
>used in the logging application.
>
>for example, let's say i have application1 running on "host1"
>so i set MDC.put("hostname", "host1") in my application1.
>the logging application is runing on "logger", so i set
>MDC.put("hostname", "logger") there.
>
>when i log something in application1, the SocketAppender sends it to
>the SocketNode, and it gets written to the logfile by the logging
>application. but in the logfile, the logging events are tagged with
>"logger", instead of "host1".
>
>my question is: do i use the MDC and/or the network-functionality of
>log4j incorrectly, or is this the expected behaviour*? and if the
>latter is the case, is there some other way to get some sort of
>"tagging" for my log statements?
>
>thanks for your time,
>
>rick
>
>* the log4j api doc says about the SocketNode: "These logging events
>are logged according to local policy, as if they were generated
>locally.", which suggests that the local MDC is used?
>
>|-
>| 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: Ceki Gulcu [mailto:ceki@qos.ch]
> > Sent: Friday, July 26, 2002 4:22 PM
> > To: Log4J Users List
> > Subject: Re: mdc & remote logging - DOH!
> >
> >
> >
> > Rick,
> >
> > What is the architecture? In the following text everything seems to
> > be a server, so it is not easy to understand your architecture nor
> > your question. Can you please clarify?
> >
> > At 13:15 26.07.2002 +0200, peter riegersperger wrote:
> > >-----BEGIN PGP SIGNED MESSAGE-----
> > >Hash: SHA1
> > >
> > >hi all!
> > >
> > >we are working on a distributed application (running on multiple
> > >servers) that should facilitate a remote logging system.
> > >
> > >that centralized logging should go into one logfile (since the
> > >servers actions are highly dependend on each other), so i figured
> > >the mdc would be the way to distinguish log entries from different
> > >servers. smart? nope. the mdc of the logentries gets replaced by
> > >the mdc from the logging server. if, for example, the remote
> > >server sets MDC.put("hostname","host1"), and the logging server
> > >sets
> > >MDC.put("hostname","loggingserver"), all entries from the remote
> > >server are tagged with hostname=loggingserver.
> > >
> > >after reading the javadoc, this behaviour sounds reasonable (since
> > >the socketnode treats all incoming logging events as local).
> > >
> > >i imagine that i'm not the only one developing for a distributed
> > >system. so, how do you tackle the problem of tagging your log
> > >messages?
> > >
> > >any input welcome!
> > >
> > >rick
> >
> > --
> > Ceki
> >
> >
> > --
> > To unsubscribe, e-mail:
><ma...@jakarta.apache.org>
>For additional commands, e-mail:
><ma...@jakarta.apache.org>
>
>-----BEGIN PGP SIGNATURE-----
>Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
>Comment: public key available at http://home.subnet.at/rick/pgp/
>
>iQA/AwUBPUFa/yDD9/SWDsvSEQLLKQCg38cwP+Fptb3da4fXny9j+3XModQAn2pY
>ckzo0HsTmoiXaLJ83u4L5eCV
>=+8kD
>-----END PGP SIGNATURE-----
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by Ceki Gülcü <ce...@qos.ch>.
At 17:21 26.07.2002 +0200, peter riegersperger wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>hi!
>
> > What is the architecture? In the following text everything seems to
> > be a server, so it is not easy to understand your architecture nor
> > your question. Can you please clarify?
>
>sorry for not making myself clear.
>actually, our situation is quite simple. we have multiple
>applications running on multiple hosts. every application uses log4j
>and a SocketAppender connecting to our logging application.
>the logging application has SocketNodes in several threads running
>(one SocketNode for each connecting application). the logging
>application writes all entries (including its own logging statements)
>into a file.
>
>In the applications, we put some information into the MDC to identify
>the source of the log entry. but (as stated in my original mail), the
>MDC in the log entry from the application gets overwritten by the MDC
>used in the logging application.
>
>for example, let's say i have application1 running on "host1"
>so i set MDC.put("hostname", "host1") in my application1.
>the logging application is runing on "logger", so i set
>MDC.put("hostname", "logger") there.
>
>when i log something in application1, the SocketAppender sends it to
>the SocketNode, and it gets written to the logfile by the logging
>application. but in the logfile, the logging events are tagged with
>"logger", instead of "host1".
That should not be the case. You should see host1. Let me double check.
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: mdc & remote logging - DOH!
Posted by peter riegersperger <ri...@subnet.at>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi!
> What is the architecture? In the following text everything seems to
> be a server, so it is not easy to understand your architecture nor
> your question. Can you please clarify?
sorry for not making myself clear.
actually, our situation is quite simple. we have multiple
applications running on multiple hosts. every application uses log4j
and a SocketAppender connecting to our logging application.
the logging application has SocketNodes in several threads running
(one SocketNode for each connecting application). the logging
application writes all entries (including its own logging statements)
into a file.
In the applications, we put some information into the MDC to identify
the source of the log entry. but (as stated in my original mail), the
MDC in the log entry from the application gets overwritten by the MDC
used in the logging application.
for example, let's say i have application1 running on "host1"
so i set MDC.put("hostname", "host1") in my application1.
the logging application is runing on "logger", so i set
MDC.put("hostname", "logger") there.
when i log something in application1, the SocketAppender sends it to
the SocketNode, and it gets written to the logfile by the logging
application. but in the logfile, the logging events are tagged with
"logger", instead of "host1".
my question is: do i use the MDC and/or the network-functionality of
log4j incorrectly, or is this the expected behaviour*? and if the
latter is the case, is there some other way to get some sort of
"tagging" for my log statements?
thanks for your time,
rick
* the log4j api doc says about the SocketNode: "These logging events
are logged according to local policy, as if they were generated
locally.", which suggests that the local MDC is used?
|-
| 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: Ceki Gulcu [mailto:ceki@qos.ch]
> Sent: Friday, July 26, 2002 4:22 PM
> To: Log4J Users List
> Subject: Re: mdc & remote logging - DOH!
>
>
>
> Rick,
>
> What is the architecture? In the following text everything seems to
> be a server, so it is not easy to understand your architecture nor
> your question. Can you please clarify?
>
> At 13:15 26.07.2002 +0200, peter riegersperger wrote:
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >hi all!
> >
> >we are working on a distributed application (running on multiple
> >servers) that should facilitate a remote logging system.
> >
> >that centralized logging should go into one logfile (since the
> >servers actions are highly dependend on each other), so i figured
> >the mdc would be the way to distinguish log entries from different
> >servers. smart? nope. the mdc of the logentries gets replaced by
> >the mdc from the logging server. if, for example, the remote
> >server sets MDC.put("hostname","host1"), and the logging server
> >sets
> >MDC.put("hostname","loggingserver"), all entries from the remote
> >server are tagged with hostname=loggingserver.
> >
> >after reading the javadoc, this behaviour sounds reasonable (since
> >the socketnode treats all incoming logging events as local).
> >
> >i imagine that i'm not the only one developing for a distributed
> >system. so, how do you tackle the problem of tagging your log
> >messages?
> >
> >any input welcome!
> >
> >rick
>
> --
> Ceki
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
Comment: public key available at http://home.subnet.at/rick/pgp/
iQA/AwUBPUFa/yDD9/SWDsvSEQLLKQCg38cwP+Fptb3da4fXny9j+3XModQAn2pY
ckzo0HsTmoiXaLJ83u4L5eCV
=+8kD
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: mdc & remote logging - DOH!
Posted by Ceki Gülcü <ce...@qos.ch>.
Rick,
What is the architecture? In the following text everything seems to be
a server, so it is not easy to understand your architecture nor your
question. Can you please clarify?
At 13:15 26.07.2002 +0200, peter riegersperger wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>hi all!
>
>we are working on a distributed application (running on multiple
>servers) that should facilitate a remote logging system.
>
>that centralized logging should go into one logfile (since the
>servers actions are highly dependend on each other), so i figured the
>mdc would be the way to distinguish log entries from different
>servers. smart? nope. the mdc of the logentries gets replaced by the
>mdc from the logging server. if, for example, the remote server sets
>MDC.put("hostname","host1"), and the logging server sets
>MDC.put("hostname","loggingserver"), all entries from the remote
>server are tagged with hostname=loggingserver.
>
>after reading the javadoc, this behaviour sounds reasonable (since
>the socketnode treats all incoming logging events as local).
>
>i imagine that i'm not the only one developing for a distributed
>system. so, how do you tackle the problem of tagging your log
>messages?
>
>any input welcome!
>
>rick
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>