New logger and level elements are not fully 'compatible' with old category
and priority (some attribute like class are now not supported), the order
of elements is changhed, there is no loggerFactory elements, etc. etc.
Anyone knows where can I find some documentation about differences in
Sub-classing of the Logger class is discouraged because it is a very
problematic feature. Consequently, XML config scripts do not support
the class attribute in logger element. However, your old
configuration scripts will continue to work since the category
element still has the class
First of all, thanks for RepositorySelector clue.
Just to clarify the sense of my message: it was not a critic, just a help
request! :-)
You know, I met log4j so long ago, and I found it very very useful for a
large range of problems.
So I think I'm not a 'casual developer' and I'm sure that
As far as java.io, I was simply repeating what is stated in the spec.
It doesn't prevent bean writers from using the package anyway, but doing
so introduces the risk of performance issues and reduced protability.
Explicit thread synchronization may work if your container provider
hasn't
I was reading the Log4j manual and it suggests that for each webapp, you
should use a separate log4j jar file in each WEB-INF/lib to make sure that
each log4j is in its own log4j Universe. However, this puts constraints
on where I put my libraries that use log4j. For instance, if I have
Howdy,
I don't know the answer, but I wanted to say I'm very interested in this question as
well. Mr. Gülcü or anyone else care to comment? ;)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 8:52 AM
Hi;
I have sent remove messages twice and I keep getting e-mails. Any idea how
to get removed?
thanks - dave
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
The reason that it should be in WEB-INF/lib not int TOMCAT_HOME/lib is
that log4j used to have problems loading the config file if you used the
server library path.
This is because the server classloader cannot see anything in the
application classloader.
If you are using a single
Hi,
I know this is a minor bug, but in the description of the doConfigure
method a /i is missing so all subsequent info is in italics.
Bye,
Helma van der Linden
Medical Informatics
University Maastricht
The Netherlands
Tel: +31 43 3882235
Fax: +31 43 3884170
[EMAIL PROTECTED]
--
To
One solution that I suggest is, store all 5 logger instances in hashtable,
store this hashtable into session and every process that wants to log
information will first retreive the handle to the logger instance by passing
some unique parameter.
The disadvantage of this method is that for every
At 11:48 30.05.2002 +0200, Giuseppe Madonna wrote:
However I wonder, to avoid Logger subclassing, why not make it final?
But it was just a thought...
Logger class is not final because Logger sub-classing allows very
important enhancements such as security or transparent logging domains.
Domains
I am starting to work with these as well...I have a simple example running
but there are some little 'tricks' --- like you get into an infinite loop if
everything is not set up properly because your SocketNodes start sending
their messages out to themselves (thats fun!).
Anyway, I got a zip file
Thanks!
At 15:32 30.05.2002 +0200, [EMAIL PROTECTED] wrote:
Hi,
I know this is a minor bug, but in the description of the doConfigure
method a /i is missing so all subsequent info is in italics.
Bye,
Helma van der Linden
--
Ceki
SUICIDE BOMBING - A CRIME AGAINST HUMANITY
Sign the petition:
reportedly, there were some problems with the mail servers at jakarta.
I don't know when it will be fixed.
At 07:13 30.05.2002 -0600, David Thielen wrote:
Hi;
I have sent remove messages twice and I keep getting e-mails. Any idea how
to get removed?
thanks - dave
--
Ceki
SUICIDE BOMBING - A
Also consider, albeit poor practice, how much working EJB code you've seen
that uses System.out and/or System.err. Clearly, these are (and must be)
java.io.PrintStream instances. Furthermore, all implementations I've seen of
PrintStream are internally synchronized to prevent output from multiple
However I wonder, to avoid Logger subclassing, why not make it final?
But it was just a thought...
Logger class is not final because Logger sub-classing allows very
important enhancements such as security or transparent logging domains.
Domains are a secret feature planned for log4j 1.3.
Jake,
Very good question.
Log4j 1.2 introduced the concept of RepositorySelectors specifically
to deal with this problem. Unless the container does for you (which
Tomcat does not) you'd have to write your own RepositorySelector.
Writing a selector is trivial if you control the application
Hi Mark,
From what I read it seems not very simple to use the SocketHubAppender.
You wrote that Lumbermill probably will need some modification in order to
work with the socketHubAppender. Is this also the case for Chainsaw or LF5?
How did you use the socketHubAppender?
Regards
Jeroen
You
If MyLogger introduces a new method that your code uses, then your
code is tied to MyLogger. It is *expecting* to use a MyLogger
instance. Your code won't work with any other Logger class.
At the same time, when you write
Logger l = Logger.getLogger()
you don't actually know the type
There is also the SimpleSocketServer class which might serve as a better
example than SocketNode itself.
-Mark
-Original Message-
From: Klein, Scott @ TW [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 7:51 AM
To: 'Log4J Users List'
Subject: RE: SocketAppender (was:
Jeroen,
Yes, unfortunately, this is the case right now. All of the client tools are
geared to supporting SocketAppender (actually I have not looked at LF5
closely enough yet, but I assume it is the case). I have a copy of Chainsaw
that I modified to support connecting to a SocketHubAppender.
Hello Ceki,
So, being somewhat new with Log4j, are you saying that given the fact
that Tomcat does not do RepositorySelectors for me and also doesn't
give me control of the context, that it would be pretty difficult to
figure out how to write a custom RepositorySelector? Are there any
examples
Hi ,
RollingFileAppender peAppender = new
RollingFileAppender(defaultPattern,/LOG/temp.log,true);
The above line throws java.io.FileNotFoundException if the directory is
not present. How do you make log4j create the directory if it is not
present?
Thanx,
Rajan
You have to code it yourself.
--
Thomas
| -Original Message-
| From: Rajan Annadurai [mailto:[EMAIL PROTECTED]]
| Sent: 30 May 2002 19:08
| To: [EMAIL PROTECTED]
| Subject: java.io.FileNotFoundException: /LOG/temp.log (The system cannot
| find the path specified)
|
|
| Hi ,
|
|
|
Hi all,
I've created a couple custom appenders, but when deployed with my app on
WebSphere, I realized I have a classpath issue: Log4J is on the JVM classpath,
but the app is not. Therefore, Log4J cannot see these custom appenders.
Our admins (for good reasons) may be hesitant to allow
check out:
http://www.theserverside.com/resources/articles/ClassLoading/article.html It
speaks about j2ee 1.3 class loading scheme and the implementations provided
by weblogic 6.1 SP2, WebSphere 4.0, and HP-AS 8. In it there is discussion
of adding ejb dependant jars into the jar manifest
Hello Andrew,
Check if websphere has a propietary method of specifiying additions to
the classpath for each componet. That way you can put log4j in all
classpath without bothering the sysadmins.
Thursday, May 30, 2002, 2:55:27 PM, you wrote:
AT Hi all,
AT I've created a couple custom
Try log4j version 1.2.3. Depending on how WL sets the Thread
Context Loader you might not need to do anything. This is 1.2.3 only.
Let us know if it works.
At 11:55 30.05.2002 -0700, Andrew Tumpach wrote:
Hi all,
I've created a couple custom appenders, but when deployed with my app on
HI all,
I'm trying to use wrapper classes for logging, I have 5 different loggers, when I try
to log, Logger.log(Priority, msg); then the message is written to all log files, just
before I'm printing logger name, but LogManager.getCurrentLoggers() returns all five
loggers, what could be the
can you put up your config file?
i think you are describing the same issue i had - it has to do with the
appender additivity rule perhaps.
-Original Message-
From: Anand M S [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 3:37 PM
To: [EMAIL PROTECTED]
Subject: LogManager
HI
Ceki,
Wouldn't this be another good example of a case where allowing your own
repository selector is a good idea?
I discussed this before:
http://marc.theaimsgroup.com/?t=10148577083r=1w=2
I suggest that until 1.3 is released (which *should* deal with this
problem by having separate
31 matches
Mail list logo
