Update to JBoss 2.4.0 or just drop in the newer log4j.jar into lib/ext. This
works for me. Send any follow to [EMAIL PROTECTED]
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 07, 2001 9:09 AM
Subject: Log4j with JBoss
> Is anyone using Log
Absolutely right Ceki. Think about using log4j in an application server.
No way should a general logging framework attempt to take down a VM.
- Original Message -
From: "Ceki Gülcü" <[EMAIL PROTECTED]>
To: "LOG4J Users Mailing List" <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 9:07 AM
The only difference between InheritableThreadLocal and ThreadLocal occurs
when the thread local variable is initialized. Accessing/setting the value is
the same in both cases. Here is a simple example:
public final class SecurityAssociation
{
private static ThreadLocal thread_principal = new
> The problem that has been hashed over and over is that classes loaded
> from jars in WEB-INF/lib or tomcat's lib don't see WEB-INF/lib or
> WEB-INF/classes. There are no class loader games you can play to change
> this as far as I know. Certainly Category's classloader won't help any
> here.
>
Using a file resource in a web-app descriptor means that one has to potentially
change the file property for each deployment. Its much easier to be able to load
the log4j.properties as a resource from the classpath than a file imho. You
also may not even have access to a file system because loggin
That is what I meant by Category as well. You should be seeing one
org.apache.log4j.Category created for each unique value passed to
getInstance(). I don't know why this would not show up in profiling.
>
> I'm sorry, by Category I mean "org.apache.log4j.Category" objects, not
> to be confused wi
I don't think its an issue even when you do have one Category per class. I was
just pointing out that you can use less than one Category per class.
- Original Message -
From: "Johnson, Clay" <[EMAIL PROTECTED]>
To: "'LOG4J Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Wednesday, April 0
You don't have to follow the pattern of having a Category instance per
class. I use one Category per package and sometimes one Category
for a logical grouping of packages.
- Original Message -
From: "L. Scott Emmons" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 04,
This is a correct assessment of the need. I have such a feature in a custom logging
framework that I have created that is very similar to log4j. In that logging framework
the equivalent of the NDC allows you to push an override priority in addition to
a context name and any logmsg issued within th
quot;LOG4J Users Mailing List" <[EMAIL PROTECTED]>
Sent: Saturday, February 17, 2001 12:46 PM
Subject: Re: Using NDC to enable logging over a thread of control
> I've never tried the NDC approach before... do you think it would work?
>
>
> On Friday, February 16, 2001,
;. One technique for doing this is to always get an
instance of a category for logging in your
application, but it depends if the user is on the debug list or not if calls go to the
special log. You can put that instance of the
Category into the request attributes.
Let me know if I'm misinterpr
little more detail? Do you want to correlate messages with
>Threads
> or with clients?
>
> -Chris
>
> Scott M Stark wrote:
>
> > One common logging task I use frequently in server development is the ability to
> > enable logging across a thread of control beginn
One common logging task I use frequently in server development is the ability to
enable logging across a thread of control beginning at some entry point. An example
is enabling all log msgs regardless of priority that are executed within a particular
servlet's service() method. Going through the l
13 matches
Mail list logo
