One thing to remember...
If you haven't called the .configure(...), then the first call to
.getInstance(...) will invoke the default initialization. The documentation
has a multi-paragraph discussion of the rules for default initialization.
So, I won't repeat them here. However, the simplest fo
The error says it all...
java.lang.IllegalArgumentException: Illegal pattern character 'Y'
Try using lowercase y
%d{dd MMM HH:mm:ss,SSS}
For further info see the Javadoc of org.apache.log4j.PatternLayout and
java.text.SimpleDateFormat
-Original Message-
From: T Master [mailto:[EM
It's not an extension of DailyRolledFileAppender, so why would you expect it
to behave like one?
Try setting a MaxBackupIndex (according to the Javadoc on
RollingFileAppender, the default is 1):
log4j.appender.AppEventsExt.MaxBackupIndex=100
-Original Message-
From: [EMAIL PROTECTED] [m
One technique would be to assign a name to each one of
the clients. Set up each name as a category in your log4j.properties
(remember that you don't have to use classname as your Category names).
The client would pass this name in requests to the server.
When a service begins processing
Before I begin my next question... MANY THANKS on the flurry of responses to
the PropertyConfigurator discussion. I was already in the process of trying
to convince myself that the default initialization was the best way to solve
the problem (as Ceki also points out). For now, that seems to be m
The parameter to the Category.getInstance(String name) is just some name to
look for in the properties. That is, you do not HAVE to use a class name
(although that is the preffered technique). Since JSPs get translated into
servlets with a hidden classname, you can make up your own heirarchy for
Using a JSP to configure the properties would only work if the Web Container
and the EJB Container are the SAME Java Virtual Machine (otherwise they
wouldn't be sharing statics). This seems like a bad assumption to me.
Orion does support loading an EJB at startup (in the server.xml file). This
nk some clarification will be
useful to all.
Dave
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 02.October 2001 02:50
To: LOG4J Users Mailing List
Subject: Re: PropertyConfigurator.configure method in J2EE
At 16:08 01.10.2001 -0400, David Schultz wrote:
>If
While it is true that a Category can have multiple appenders, neither the
properties file definition nor the log4j.dtd have syntax for assigning a
Priority to an Appender. Priority is assigned to the Category.
Also, don't forget the inheritance of Categories. The Category
"com.lycos.subscriber.
First Question I can answer: Use %n instead of \n. %n (discussed in the
javadoc for the PropertyConfigurator class) is the OS-independent carriage
return.
Second Question gets a little stranger, but I think it helps to think of it
this way:
Where is the JVM for your Web Server executing? That'
If I understand the documentation and discussion threads properly, the
configure method of the PropertyConfigurator class should only be called
once be JVM. (Multiple calls result in multiple occurences of output data
in the logs.)
So, when using a J2EE server, where is the appropriate place for
11 matches
Mail list logo
