I am using SMTPAppender. The programs compiles well and when running gives
me an error
MailException 505: Authentication required.
I have tried the program on our server thru which we are sending all the
other system generated emails. There also it gives me the same Exception. I
am using log4j1.1.
Hello.
I'm relatively new to log4. I found from FAQ that log4j is fail-stop and it
is supposed to never throw any exception. I think that is the way it should
be. But when "some" logging operations become essential for our application,
says, the application needs to be aware of the completeness o
Thomas,
I understand your position and apologize for the trouble this bug may
have caused. Let me note that such serious programming errors
(throwing runtime exceptions) have been extremely rare. In fact, if I
recall correctly, the most recent one was in September 2000, that is
over a year ago.
At 11:17 16.12.2001 -0600, you wrote:
>One of the requirements of the project I am working on is to allow the log
>level to be overriden on a user-by-user basis. The idea, for example, is
>that all logging levels get set to WARN in our production environment;
>however when an issue comes up, I c
Excellent. Works a treat.
--On Sunday, 16 December 2001 10:17 a.m. -0800 doug b <[EMAIL PROTECTED]>
wrote:
> Enumeration iterator =
--
Mark DerricuttE-Mail: [EMAIL PROTECTED]
Senior Delphi DeveloperICQ: 19348533
Ti
Ceki,
I respect your opinion, but in my case this error could possibly have
brought down a mission-critiacal telephony system serving thousands of
users.
In general a logging library such as Log4j should be extremely conservative
exposing bugs in a way that results in process failure and system
we use:
// log4j simple/default setup iff
// no other Appenders already configured
Enumeration iterator =
Category.getRoot().getAllAppenders();
if (!iterator.hasMoreElements())
{
BasicConfigurator.configure();
}
--- Mark Derricutt <[EMAIL PR
One of the requirements of the project I am working on is to allow the log
level to be overriden on a user-by-user basis. The idea, for example, is
that all logging levels get set to WARN in our production environment;
however when an issue comes up, I can override the WARN level to DEBUG for
my
Thomas,
This is a very interesting comment. I disagree with it for the
following reason. Wrapping the error in a try and catch block places
bugs behind a smoke screen effectively burying them, such that they
become much harder to detect. I do not fear bugs, only the insidious
ones.
Consider the
Thanx, Ceki.
Again, allow me to suggest that the loop in Dispatcher is guarded by a
try/catch block, thus preventing it from exiting disgracefully.
--
Thomas
| -Original Message-
| From: Ceki Gulcu [mailto:[EMAIL PROTECTED]]
| Sent: 14 December 2001 22:11
| To: Log4J Users List
| Subje
10 matches
Mail list logo
