Jake, you are right, I sent only the partial config. I got all this stuff as a
heritage and now trying to investigate it. There is the full config:
log4j.rootCategory=INFO, CONSOLE, FILE
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
#log4j.appender.CONSOLE.Threshold=${org.apache.geronimo.log.ConsoleLogLevel}
log4j.appender.CONSOLE.Threshold=WARN
log4j.appender.CONSOLE.Target=System.out
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n
log4j.appender.FILE=org.apache.log4j.RollingFileAppender
log4j.appender.FILE.threshold=DEBUG
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n
#
# Note, changing log4j.appender.FILE.append=false will result in logs being
# overwritten without archiving the previous version of the log.
#
log4j.appender.FILE.append=true
log4j.appender.FILE.file=${org.apache.geronimo.base.dir}/var/log/server.log
log4j.appender.FILE.bufferedIO=false
log4j.appender.FILE.maxBackupIndex=3
log4j.appender.FILE.maxFileSize=10MB
#
# Example: enable trace logging from CONSOLE appender
#
#log4j.appender.CONSOLE.Threshold=TRACE#org.apache.geronimo.system.logging.log4j.XLevel
#
# Example: enable trace messages from foo.bar category
#
#log4j.category.foo.bar=TRACE#org.apache.geronimo.system.logging.log4j.XLevel
#### Show key debug messages in the log ####
log4j.category.org.apache.geronimo.gbean.runtime.GBeanSingleReference=DEBUG
#### Eliminate any INFO level output during normal operation -- except the
really relevant stuff ####
# We can change the Geronimo code to avoid this, but we have to just adjust
the log levels for
# any third-party libraries.
log4j.category.org.apache.commons.digester=ERROR
log4j.category.org.apache.jasper.compiler.SmapUtil=WARN
# ActiveMQ
log4j.category.org.activemq.ActiveMQConnection=WARN
log4j.category.org.activemq.store.jdbc.adapter.DefaultJDBCAdapter=WARN
log4j.category.org.activemq.store.jdbc.JDBCPersistenceAdapter=WARN
log4j.category.org.activemq.store.journal.JournalPersistenceAdapter=WARN
log4j.category.org.activemq.broker.impl.BrokerContainerImpl=WARN
log4j.category.org.activemq.broker.impl.BrokerConnectorImpl=WARN
log4j.category.org.activemq.transport.tcp.TcpTransportChannel=ERROR
log4j.category.org.activemq.transport.tcp.TcpTransportServerChannel=WARN
log4j.category.org.activemq.transport.vm.VmTransportServerChannel=WARN
# Don't need so much info on every web page that's rendered
log4j.category.org.mortbay=INFO
log4j.category.org.apache.pluto=INFO
log4j.category.org.apache.jasper=INFO
# Various Jetty startup/shutdown output
log4j.category.org.mortbay.http.HttpServer=WARN
log4j.category.org.mortbay.http.SocketListener=WARN
log4j.category.org.mortbay.http.ajp.AJP13Listener=WARN
log4j.category.org.mortbay.util.Container=WARN
log4j.category.org.mortbay.util.Credential=WARN
log4j.category.org.mortbay.util.ThreadedServer=WARN
log4j.category.org.mortbay.jetty.servlet.WebApplicationContext=WARN
log4j.category.org.mortbay.jetty.context=WARN
# Various Tomcat startup output
log4j.category.org.apache.catalina.realm.JAASRealm=WARN
log4j.category.org.apache.catalina.realm.RealmBase=WARN
log4j.category.org.apache.catalina.loader.WebappLoader=WARN
log4j.category.org.apache.catalina.loader.WebappClassLoader=WARN
log4j.category.org.apache.catalina.startup.Embedded=WARN
log4j.category.org.apache.catalina.core.StandardEngine=WARN
log4j.category.org.apache.catalina.core.StandardHost=WARN
log4j.category.org.apache.jk.common.ChannelSocket=WARN
log4j.category.org.apache.jk.server.JkMain=WARN
log4j.category.org.apache.coyote.http11.Http11BaseProtocol=WARN
log4j.category.org.apache.coyote.http11.Http11Protocol=WARN
log4j.category.org.apache.catalina.core.ContainerBase=WARN
log4j.category.org.apache.catalina.core.StandardContext=WARN
log4j.category.org.apache.tomcat.util.net.SSLImplementation=WARN
# Enable the following for Tomcat Cluster logging
#log4j.category.org.apache.catalina.cluster=INFO
# Emits a spurious WARN during startup on /some-path/* security mappings
log4j.category.org.apache.catalina.deploy.SecurityCollection=ERROR
# Prints the MBean Server ID
log4j.category.javax.management.MBeanServerFactory=WARN
# Prints the RMI connection URL
log4j.category.javax.management.remote.rmi.RMIConnectorServer=WARN
log4j.category.javax.management.remote.JMXServiceURL=WARN
# Prints various stuff during startup
log4j.category.org.apache.juddi.registry.RegistryServlet=WARN
# Prints various stuff when the portal is used
log4j.category.org.apache.pluto.portalImpl.Servlet=WARN
# Prints stuff for AJAX calls
log4j.category.uk.ltd.getahead.dwr.impl.DefaultConfiguration=WARN
log4j.category.uk.ltd.getahead.dwr.impl.ExecuteQuery=WARN
log4j.category.uk.ltd.getahead.dwr.util.Logger=WARN
# Various Axis log output
log4j.category.org.apache.axis.enterprise=INFO
log4j.category.org.apache.axis.TIME=OFF
log4j.category.org.apache.axis.EXCEPTIONS=INFO
log4j.appender.NETCOOL=org.apache.log4j.RollingFileAppender
log4j.appender.NETCOOL.threshold=DEBUG
log4j.appender.NETCOOL.layout=org.apache.log4j.PatternLayout
log4j.appender.NETCOOL.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m%n
log4j.appender.NETCOOL.append=true
log4j.appender.NETCOOL.file=${org.apache.geronimo.base.dir}/../log/netcool.log
log4j.appender.NETCOOL.bufferedIO=false
log4j.appender.NETCOOL.maxBackupIndex=3
log4j.appender.NETCOOL.maxFileSize=10MB
# set the default priority to INFO for all micromuse/ibm loggers
log4j.category.com.ibm.tivoli=INFO,NETCOOL
log4j.category.com.micromuse=INFO,NETCOOL
# override any specific loggers
log4j.category.com.micromuse.common.util.Debug=DEBUG
log4j.additivity.com.ibm.tivoli=false
log4j.additivity.com.micromuse=false
Best wishes,
Dmitry Surovtsev
-----Original Message-----
From: Jacob Kjome [mailto:[email protected]]
Sent: Friday, February 20, 2009 1:19 AM
To: Log4J Users List
Subject: Re: Filtering duplicated log-messages
What appender is outputting these duplicate logs? What you provided doesn't
look to me like it matches the conversion pattern of the NETCOOL appender.
Don't you configure the root logger? Seems like you are witholding some of
your config. Also note that "category" is deprecated. You should use
"logger" and "rootLogger".
Jake
On Thu, 19 Feb 2009 09:38:21 +0200
"Surovtsev, Dmytro" <[email protected]> wrote:
> Thanks for reply :-)
>
> The matter is addittivity IS set to false, there is a config:
>
> log4j.appender.NETCOOL=org.apache.log4j.RollingFileAppender
> log4j.appender.NETCOOL.threshold=DEBUG
> log4j.appender.NETCOOL.layout=org.apache.log4j.PatternLayout
> log4j.appender.NETCOOL.layout.ConversionPattern=%d{ABSOLUTE} %-5p [%c{1}]
>%m%n
> log4j.appender.NETCOOL.append=true
> log4j.appender.NETCOOL.file=${org.apache.geronimo.base.dir}/../log/netcool.log
> log4j.appender.NETCOOL.bufferedIO=false
> log4j.appender.NETCOOL.maxBackupIndex=3
> log4j.appender.NETCOOL.maxFileSize=10MB
>
> # set the default priority to INFO for all micromuse/ibm loggers
> log4j.category.com.ibm.tivoli=INFO,NETCOOL
> log4j.category.com.micromuse=INFO,NETCOOL
> # override any specific loggers
> log4j.category.com.micromuse.common.util.Debug=DEBUG
> log4j.additivity.com.ibm.tivoli=false
> log4j.additivity.com.micromuse=false
>
> And again, there is a lot of duplicates:
>
> 23:06:30,516 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,519 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,578 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,579 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,596 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,639 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,640 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,793 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,795 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,854 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,855 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,915 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,917 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,976 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,978 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:30,987 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:31,037 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:31,045 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:31,110 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:31,117 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:31,177 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
> 23:06:31,178 DEBUG [Debug]
>Thread[SynchronousMessageProcessor,5,main]Returning
>jdbc:sybase:Tds:crl_os_ks1_p:4100
>
> (Skipped...)
>
> Best wishes,
> Dmitry Surovtsev
>
>
> -----Original Message-----
>From: Jacob Kjome [mailto:[email protected]]
> Sent: Thursday, February 19, 2009 8:33 AM
> To: Log4J Users List
> Cc: Log4J Developers List
> Subject: Re: Filtering duplicated log-messages
>
> Sure, by setting additivity to false. Post your config. BTW, don't post it
>to
> the log4j-dev list. post it to the log4j-user list. The dev list isn't for
> general user question, but for Log4j development issues.
>
> Jake
>
> On 2/18/2009 7:28 AM, Surovtsev, Dmytro wrote:
>> Hi all,
>>
>>
>>
>> Is it possible to filter messages going to logfile in 1.2 version? Problem:
>>
>>
>>
>> 05:00:35,932 DEBUG [Debug]
>> Thread[SynchronousMessageProcessor,5,main]Returning
>> jdbc:postgresql://crl_pg_app:5432/crl
>>
>> 05:00:35,957 DEBUG [Debug]
>> Thread[SynchronousMessageProcessor,5,main]Returning
>> jdbc:postgresql://crl_pg_app:5432/crl
>>
>> 05:00:35,963 DEBUG [Debug]
>> Thread[SynchronousMessageProcessor,5,main]Returning
>> jdbc:postgresql://crl_pg_app:5432/crl
>>
>>
>>
>> 05:00:36,002 DEBUG [Debug]
>> Thread[SynchronousMessageProcessor,5,main]Returning
>> jdbc:sybase:Tds:crl_os_ks1_p:4100
>>
>> 05:00:36,004 DEBUG [Debug]
>> Thread[SynchronousMessageProcessor,5,main]Returning
>> jdbc:sybase:Tds:crl_os_ks1_p:4100
>>
>>
>>
>> Is it possible to log only first such message and just count duplicates?
>>
>>
>>
>> TIA.
>>
>>
>>
>>
>>
>> Best wishes,
>>
>> Dmitry Surovtsev
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>> Please note: The information in this email and in any attachments is
>> confidential and may be privileged. If you are not the intended
>> recipient, please destroy this message, delete any copies held on your
>> systems and notify the sender immediately. You should not retain, copy
>> or use this email for any purpose, nor disclose all or any part of its
>> content to any other person.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>
> Please note: The information in this email and in any attachments is
>confidential and may be privileged. If you are not the intended recipient,
>please destroy this message, delete any copies held on your systems and
>notify the sender immediately. You should not retain, copy or use this email
>for any purpose, nor disclose all or any part of its content to any other
>person.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Please note: The information in this email and in any attachments is
confidential and may be privileged. If you are not the intended recipient,
please destroy this message, delete any copies held on your systems and notify
the sender immediately. You should not retain, copy or use this email for any
purpose, nor disclose all or any part of its content to any other person.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
