Re: problem with JDBC logging
These seems like a post made long ago. Though, I have the same problem and wants to know if you solved this or if anybody has an idea? I can't seem to figure out what arguments to insert with 'logger.log(?)' to get the unique information in all columns that I want to. -- View this message in context: http://old.nabble.com/problem-with-JDBC-logging-tp20513136p29448546.html Sent from the Log4j - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
configuring email appending for WARN and above
Can someone tell if it is possible to configure the smtp email appender to
send email for WARN level message and above? I seem to only be able to get
ERROR level stuff to come back in email form.
log4j.appender.email=org.apache.log4j.net.SMTPAppender
log4j.appender.email.SMTPHost=smtp.server
log4j.appender.email.SMTPDebug=false
log4j.appender.email.bufferSize=1
log4j.appender.email.from=f...@domain.com
log4j.appender.email.to...@domain.com
log4j.appender.email.subject=subject
log4j.appender.email.threshold=WARN
log4j.appender.email.layout=org.apache.log4j.PatternLayout
log4j.appender.email.layout.ConversionPattern=[%p]
%d{ISO8601}%n%n%c:%L%n%n%m%n
--
Curtis
Unable to shutdown SocketHubReceivers in Chainsaw
Hi Scott Using latest Chainsaw (you made the fix for removeing loggers from the logger pane), I have setup to SocketHubAppenders and 2 SocketHubReceivers The first pair SocktHubAppender is connected with the logs from org.apache.* and shall log all log events from org.apache.Tomcat e all It connects well to Port 4447 from my PC running chainsaw to my server running tomcat e all. The second is more specific and shall log from my axawl.spezpla.servers.SpezplaService.SpServer logger When Tomcat starts the first pair works OK, the SocketHubReceiver connects (attempst to connect) on a 1 second interval and It gets data from all the logers spread within apache jakarta tomcat e all. (It's very usefull to learn about loggers in Tomcat Catalina Jk ... do it using chainsaw) The second pair does not work at all. I can see in the chainsaw status line Connection received from Integ1:4448 But then I can also see in the chainsaw-log Remote host refused Connection But no log output is generated into Chainsaw, no taged pane for the messages of the second receiver is created. All is OK down to the bolded Line when the confirmation comes that the tomcat server has been starting up. After that line I start my axis2 client. And by doing so, the axis2 web service SpServer object, catches infomrmation from a log4j.properties file in the axis2 class directory. This properties and the code work well if I use SocketAppender and SocketReceivers. But see what happens when I use SocketHubAppender's and Receivers and what to create a port 4448 for the web service SocketHubAppender The first red line bothers me as it closes the Chainsaw_client and hence I do not see any more logging from tomcat e all. It happens at the time the axis2 log4j.properties is read by my web service SpServer objetc. The second red line shows that correctly Chainsaw_axis2 is configured with ist unique port 4448 However later on I get errors raised and dont know why, and no log events are sent using the chainsaw_axis2 client. Any advise is very welcome Josef IA64ty APACHE$JAKARTA_SERVER_OUTPUT.LOG $ Set NoOn $ VERIFY = F$VERIFY(F$TRNLNM(SYLOGIN_VERIFY)) Using CATALINA_BASE : /disk$oracle2/apache/jakarta/tomcat/ Using CATALINA_HOME : /disk$oracle2/apache/jakarta/tomcat/ Using CATALINA_TMPDIR: /disk$oracle2/apache/jakarta/tomcat/temp APACHE$ROOT:[00] = APACHE$SPECIFIC:[00] = APACHE$COMMON:[00] P1 = RUN P2 = P3 = P4 = P5 = P6 = P7 = P8 = java_vms_base = INTEG1$DKB3:[00.JAVA$150. JAVA_HOME = /INTEG1$DKB3/00/JAVA$150 SYSTEM_CLASSPATH = INTEG1$DKB3:[00.JAVA$150.LIB]TOOLS.JAR Using Java 1.5.0 setup -- $ @sys$manager:java$150_setup Running Tomcat. 0: integ1$dkb3:[00.java$150.bin]java$java.exe;1 1: -Xms64m 2: -Xmx1024m 3: -Xdynclassgc 4: -Xint 5: -Djava.compiler=NONE 6: -Djava.util.logging.config.file=/catalina_home/common/classes/commons-lo gging.properties 7: -Djava.endorsed.dirs=/disk$oracle2/apache/jakarta/tomcat/common/endorsed 8: -Dcatalina.base=/disk$oracle2/apache/jakarta/tomcat/ 9: -Dcatalina.home=/disk$oracle2/apache/jakarta/tomcat/ 10: -Dcatalina.tmpdir=/disk$oracle2/apache/jakarta/tomcat/temp 11: org.apache.catalina.startup.Bootstrap 12: start log4j: Parsing for [root] with value=[INFO, CONSOLE, R, CHAINSAW_CLIENT]. log4j: Level token is [INFO]. log4j: Category root set to INFO log4j: Parsing appender named CONSOLE. log4j: Parsing layout options for CONSOLE. log4j: Setting property [conversionPattern] to [%d %-5p %c - %m%n]. log4j: End of parsing for CONSOLE. log4j: Parsed CONSOLE options. log4j: Parsing appender named R. log4j: Parsing layout options for R. log4j: Setting property [conversionPattern] to [%p %t %c - %m%n ]. log4j: End of parsing for R. log4j: Setting property [append] to [true]. log4j: Setting property [file] to [/disk$oracle2/apache/jakarta/tomcat/logs/tomcat.log]. log4j: Setting property [maxBackupIndex] to [10]. log4j: Setting property [maxFileSize] to [2MB ]. log4j: setFile called: /disk$oracle2/apache/jakarta/tomcat/logs/tomcat.log, true log4j: setFile ended log4j: Parsed R options. log4j: Parsing appender named CHAINSAW_CLIENT. log4j: Setting property [port] to [4447]. log4j: Setting property [locationInfo] to [true]. log4j: Parsed CHAINSAW_CLIENT options. log4j: Parsing for [org.apache.tomcat] with value=[INFO, CONSOLE, R, CHAINSAW_CLIENT]. log4j: Level token is [INFO]. log4j: Category org.apache.tomcat set to INFO log4j: Parsing appender named CONSOLE. log4j: Appender CONSOLE was already parsed. log4j: Parsing appender named R. log4j: Appender R was already parsed. log4j: Parsing appender named CHAINSAW_CLIENT. log4j: Appender CHAINSAW_CLIENT was already parsed. log4j: Handling log4j.additivity.org.apache.tomcat=[null] log4j: Parsing for [org.apache.jasper] with value=[INFO, CONSOLE, R, CHAINSAW_CLIENT]. log4j: Level token is [INFO]. log4j: Category org.apache.jasper set to INFO log4j: Parsing appender named CONSOLE. log4j: Appender
Re: configuring email appending for WARN and above
This is documented in the SMTPAppender Javadoc [1].
log4j.appender.email.EvaluatorClass=com.mypackage.MyCustomTriggeringEventEvaluator
...where the latter class implements TriggeringEventEvaluator [2].
[1]
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/net/SMTPAppender.html
[2]
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/spi/TriggeringEventEvaluator.html
Jake
On Mon, 16 Aug 2010 12:25:42 -0500
Curtis Garman curt.gar...@gmail.com wrote:
Can someone tell if it is possible to configure the smtp email appender to
send email for WARN level message and above? I seem to only be able to get
ERROR level stuff to come back in email form.
log4j.appender.email=org.apache.log4j.net.SMTPAppender
log4j.appender.email.SMTPHost=smtp.server
log4j.appender.email.SMTPDebug=false
log4j.appender.email.bufferSize=1
log4j.appender.email.from=f...@domain.com
log4j.appender.email.to...@domain.com
log4j.appender.email.subject=subject
log4j.appender.email.threshold=WARN
log4j.appender.email.layout=org.apache.log4j.PatternLayout
log4j.appender.email.layout.ConversionPattern=[%p]
%d{ISO8601}%n%n%c:%L%n%n%m%n
--
Curtis
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
Re: configuring email appending for WARN and above
Thanks, Jacob...I'll investigate this.
On Mon, Aug 16, 2010 at 1:06 PM, Jacob Kjome h...@visi.com wrote:
This is documented in the SMTPAppender Javadoc [1].
log4j.appender.email.EvaluatorClass=com.mypackage.MyCustomTriggeringEventEvaluator
...where the latter class implements TriggeringEventEvaluator [2].
[1]
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/net/SMTPAppender.html
[2]
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/spi/TriggeringEventEvaluator.html
Jake
On Mon, 16 Aug 2010 12:25:42 -0500
Curtis Garman curt.gar...@gmail.com wrote:
Can someone tell if it is possible to configure the smtp email appender to
send email for WARN level message and above? I seem to only be able to get
ERROR level stuff to come back in email form.
log4j.appender.email=org.apache.log4j.net.SMTPAppender
log4j.appender.email.SMTPHost=smtp.server
log4j.appender.email.SMTPDebug=false
log4j.appender.email.bufferSize=1
log4j.appender.email.from=f...@domain.com
log4j.appender.email.to...@domain.com
log4j.appender.email.subject=subject
log4j.appender.email.threshold=WARN
log4j.appender.email.layout=org.apache.log4j.PatternLayout
log4j.appender.email.layout.ConversionPattern=[%p]
%d{ISO8601}%n%n%c:%L%n%n%m%n
--
Curtis
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
--
Curtis Garman
Re: Unable to shutdown SocketHubReceivers in Chainsaw
It appears you are loading a new log4j configuration inside the same VM. These lines in your log are due to a call to appender.close, which is called by removeAllAppenders, possibly due to PropertyConfigurator parsing the AXIS2 log4j.properties config file. log4j: closing SocketHubAppender CHAINSAW_CLIENT log4j: stopping ServerSocket log4j: server monitor thread shutting down log4j: server monitor thread shut down log4j: closing client connections log4j: SocketHubAppender CHAINSAW_CLIENT closed Can you use a single log4j.properties file which combines all entries (including SocketHubAppender) into one config file which is read on Tomcat startup? That may resolve your issue.. Scott On Mon, Aug 16, 2010 at 11:06 AM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Hi Scott Using latest Chainsaw (you made the fix for removeing loggers from the logger pane), I have setup to SocketHubAppenders and 2 SocketHubReceivers The first pair SocktHubAppender is connected with the logs from org.apache.* and shall log all log events from org.apache.Tomcat e all It connects well to Port 4447 from my PC running chainsaw to my server running tomcat e all. The second is more specific and shall log from my axawl.spezpla.servers.SpezplaService.SpServer logger When Tomcat starts the first pair works OK, the SocketHubReceiver connects (attempst to connect) on a 1 second interval and It gets data from all the logers spread within apache jakarta tomcat e all. (It's very usefull to learn about loggers in Tomcat Catalina Jk ... do it using chainsaw) The second pair does not work at all. I can see in the chainsaw status line Connection received from Integ1:4448 But then I can also see in the chainsaw-log Remote host refused Connection But no log output is generated into Chainsaw, no taged pane for the messages of the second receiver is created. All is OK down to the bolded Line when the confirmation comes that the tomcat server has been starting up. After that line I start my axis2 client. And by doing so, the axis2 web service SpServer object, catches infomrmation from a log4j.properties file in the axis2 class directory. This properties and the code work well if I use SocketAppender and SocketReceivers. But see what happens when I use SocketHubAppender's and Receivers and what to create a port 4448 for the web service SocketHubAppender The first red line bothers me as it closes the Chainsaw_client and hence I do not see any more logging from tomcat e all. It happens at the time the axis2 log4j.properties is read by my web service SpServer objetc. The second red line shows that correctly Chainsaw_axis2 is configured with ist unique port 4448 However later on I get errors raised and dont know why, and no log events are sent using the chainsaw_axis2 client. Any advise is very welcome Josef IA64ty APACHE$JAKARTA_SERVER_OUTPUT.LOG $ Set NoOn $ VERIFY = F$VERIFY(F$TRNLNM(SYLOGIN_VERIFY)) Using CATALINA_BASE : /disk$oracle2/apache/jakarta/tomcat/ Using CATALINA_HOME : /disk$oracle2/apache/jakarta/tomcat/ Using CATALINA_TMPDIR: /disk$oracle2/apache/jakarta/tomcat/temp APACHE$ROOT:[00] = APACHE$SPECIFIC:[00] = APACHE$COMMON:[00] P1 = RUN P2 = P3 = P4 = P5 = P6 = P7 = P8 = java_vms_base = INTEG1$DKB3:[00.JAVA$150. JAVA_HOME = /INTEG1$DKB3/00/JAVA$150 SYSTEM_CLASSPATH = INTEG1$DKB3:[00.JAVA$150.LIB]TOOLS.JAR Using Java 1.5.0 setup -- $ @sys$manager:java$150_setup Running Tomcat. 0: integ1$dkb3:[00.java$150.bin]java$java.exe;1 1: -Xms64m 2: -Xmx1024m 3: -Xdynclassgc 4: -Xint 5: -Djava.compiler=NONE 6: -Djava.util.logging.config.file=/catalina_home/common/classes/commons-lo gging.properties 7: -Djava.endorsed.dirs=/disk$oracle2/apache/jakarta/tomcat/common/endorsed 8: -Dcatalina.base=/disk$oracle2/apache/jakarta/tomcat/ 9: -Dcatalina.home=/disk$oracle2/apache/jakarta/tomcat/ 10: -Dcatalina.tmpdir=/disk$oracle2/apache/jakarta/tomcat/temp 11: org.apache.catalina.startup.Bootstrap 12: start log4j: Parsing for [root] with value=[INFO, CONSOLE, R, CHAINSAW_CLIENT]. log4j: Level token is [INFO]. log4j: Category root set to INFO log4j: Parsing appender named CONSOLE. log4j: Parsing layout options for CONSOLE. log4j: Setting property [conversionPattern] to [%d %-5p %c - %m%n]. log4j: End of parsing for CONSOLE. log4j: Parsed CONSOLE options. log4j: Parsing appender named R. log4j: Parsing layout options for R. log4j: Setting property [conversionPattern] to [%p %t %c - %m%n ]. log4j: End of parsing for R. log4j: Setting property [append] to [true]. log4j: Setting property [file] to [/disk$oracle2/apache/jakarta/tomcat/logs/tomcat.log]. log4j: Setting property [maxBackupIndex] to [10]. log4j: Setting property [maxFileSize] to [2MB ]. log4j: setFile called: /disk$oracle2/apache/jakarta/tomcat/logs/tomcat.log, true log4j: setFile ended log4j: Parsed R options.
