On 11/27/2008 12:56 PM, Ceki Gulcu wrote:
>
>
> Thanks for your response. Comments inline.
>
> Jacob Kjome wrote:
>> Hi Ceki,
>>
>> Can you please explain your change of heart first? I'll take a guess
>> as to your
>> skepticism...
>
>> 1. Very little built in support, making repository selec
Thanks for your response. Comments inline.
Jacob Kjome wrote:
Hi Ceki,
Can you please explain your change of heart first? I'll take a guess as to your
skepticism...
1. Very little built in support, making repository selectors generally a custom
solution, which inhibits widespread use. T
Try using -Dlog4j.debug=true to see how Log4j is being configured. Maybe
someone
is performing manual configuration shortly after auto-configuration takes place?
Jake
On 11/26/2008 3:54 PM, Farrukh Najmi wrote:
> I have been using log4j 1.2.14 and commons-logging 1.1 in my project
> successfull
Hi Ceki,
Can you please explain your change of heart first? I'll take a guess as to your
skepticism...
1. Very little built in support, making repository selectors generally a custom
solution, which inhibits widespread use. This can be easily addressed.
2. The use of static loggers as well a
Hello,
I am using the SMTPAppender to send mails in case of errors. I have a
requirement to have the number of error emails limited to e.g. 10 per
minute. Is this possible with any of the standard filters?
cheers,
dirk
-
To uns
Hello Bender,
Thank you for your detailed response. I appreciate it.
I believe that the problem you describe, namely separation of logging
(per thread), can be accomplished by means other than repository
selectors.
Your requirements are duly noted. I intend to look into it and to offer a
more c
