Correct. The log4j.debug property output only goes to standard output.
On 10/27/06, Adilson Dias da Silva <[EMAIL PROTECTED]> wrote:
In localhost works ok.
Well, to get this answer really fine, i will ask host admin to see
the server's console.
Whem the system debug is on, the msg is restricted
In localhost works ok.
Well, to get this answer really fine, i will ask host admin to see
the server's console.
Whem the system debug is on, the msg is restricted only to the console ?
On 10/27/06, James Stauffer <[EMAIL PROTECTED]> wrote:
Then are you sure that log4j.xml is being found?
On
Then are you sure that log4j.xml is being found?
On 10/26/06, Adilson Dias da Silva <[EMAIL PROTECTED]> wrote:
OH, OK.
It is automatic, i do not call explicitly DOMConfigurator.
. it is in dir classes.
tks,
On 10/26/06, James Stauffer <[EMAIL PROTECTED]> wrote:
>
> Automatic: you put log4j.xml
hi,
just a tought (this might be a stupid question from me):
why would you want to do that?
if you only have few requests i see no performance need to cache
if you have large ammounts of requests then you'll get a problem when you're
writing them to the DB at the end of the day.
if you have la
It's possible. You need to create a log4j.xml config file that contains both a
LogFilePatternReceiver entry and a JDBCAppender entry.
Once you have the xml config file, you need a program that will initialize this
configuration (your app won't be generating events, just the receiver).
You can
