A Log4j Stumper, can't get logs in the right place.

[Paul Duer]

Hi guys, I want to log a process into a special log file. I setup a special category for it and I initalize it correctly. But I don't want the log statments to print in the stdout console log.
How do I do that? Here's my current log4j properties file:
#### Setup the Categories
# This is where we setup our debug levels.
# All appenders must be in this list to be initialized correctly.
# You MUST have the ', appender' for this to work!
####
log4j.rootLogger=warn,stdout
# Debug logging per class
log4j.logger.irwin.comm=debug,soap
log4j.logger.floodix=debug,soap
#### Setup the Appenders
# To add an appender, simply copy the soap section. Change all places you see 'soap' to whatever
# you want the appender to be named. Change the end of the 'File' line to the appropriate log location/name.
####
# stdout log - Use this appender if you want to use log4j to log to the console.
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d{dd MMM yyyy HH:mm:ss,SSS}] %-5p %c{1} %x - %m%n
# soap log
log4j.appender.soap=org.apache.log4j.RollingFileAppender
log4j.appender.soap.File=/logs/flood_ix.log
log4j.appender.soap.Append=true
log4j.appender.soap.MaxFileSize=1500KB
log4j.appender.soap.MaxBackupIndex=5
log4j.appender.soap.layout=org.apache.log4j.PatternLayout
log4j.appender.soap.layout.ConversionPattern=%d{yyyy/MM/dd HH:mm:ss.SSS} %p - %m%n

[Vikas Varma]

log4j.rootLogger=warn,stdout

Change the log4j property to
log4j.rootLogger=warn

[Margit Bork]

logger.setAdditivity(false);
is also a possibility, to avoid logging to a logger up the hieracy

[Margit Bork]

does i work for you to set the log4j.rootLogger to warn ?
When i try to get a logger that does not make output unles the logger is specified i fail. I mean if i havent specified the logger that i instantiate it get at default loglevel on debug - and i dont want that.
I hope it is possible to define a hieracy of loggers mirroring my class hieracy, so that i dont have to make a specific configuration for each class's logger (I want each class to have its own logger to be able to pinpoint logging in the production environment )
Any experience with this ??