n a normal log4j installation,
> and by overriding one method (executeSql()) you would probably have something that
> works great for your situation.
>
> Kevin Steppe
> Software Architect/Developer looking for work
>
> John Carnahan wrote:
>
> > Jeff,
> >
>
Jeff,
We recently did a big project using log4j and Java stored procs. I am not sure
if you have already learned this but using log4j file appenders is close to
impossible in that context. As you likely know Oracle likes to own the i/o and
consequently closes output streams very strictly after pr
Alan,
One thing we have done is to use JMS. That may be overkill for you or you
simply want to do everything in memory. Before we used JMS I just wrote a
simple FIFO queue using wait() and notify() for logging. Threads enqueueing
a message would block with wait() until the queue dropped below the
;s how it is in 1.04). I don't know why -- I just know if
> I include the "file:" it works and if I leave it off it doesn't work.
>
> -Jim Moore
>
> -Original Message-
> From: John Carnahan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, Mar
Jim,
Why is this so? Assuming the file is local, Class.getResource will
return a URL with prefix 'file' that should work regardless of whether
the file is a properties file or xml. As long as either is somewhere in
the classpath this works great. The only question that would remain is
precede
Qiqi,
The servlet side is pretty easy - as you likely already know. Use
Servlet.getServletConfig().getServletContext().getInitParameter("foo").
Then within the web-app config use . Then just
initialize the log4j system at runtime. In this way you can use a
different hierarchy for different virtua
Scott,
I do not know about overriding priority but I do know how to correlate msgs with the
active
thread. It is a bit of a hack but at the start of your service method use
Thread.setName to
something unique and identifiable. Then the log can be easily parsed by thread name.
Like I
said it see
