You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Stadelmann Josef <jo...@axa-winterthur.ch> on 2013/03/26 17:20:30 UTC
[tomcat 5.5.26] why are not all log4j.properties files parsed
we have multiple applications deployed as war files into tomcat webapps.
each apps has its class directory among a lib directory
we use log4j-1.6 and so each web apps/web-inf/classes has its
log4j.properties file
what we do not understand is the order in which tomcat deployes the
several web apps and what we do even less understand is in which order
the various log4j.properties are parsed and used. OR are they just
parsed and not used, or later used or perhaps used, I tell you "it is a
mess!"
We can clearly see that it parses
1. /catalian/lib/log4j.properties
2. then it deploys /catalina/webapps/SpezplaFS -
a. the logging is formatted with rules from
/catalian/lib/log4j.properties
b. /SpezplaFS/WEB-INF/classes/log4j.properties is never parsed
c. but therefore we can see that /catalian/lib/log4j.properties a
second time
3. and our /catalina/webapps/axis2/WEB-INF/classes/log4j.properties
is never parsed
a. but as you can see all modules and axis2.war itself is deployed
b. why is it's own properties file not parsed
4. svnkit-dav has not yet its own logging system
any hints welcome
<<log4j-parsing.txt>>
AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi Mark
1. thank you
2. it will take me a bit time to go through what your recommendations
3. your right, I made the test on tomcat 6.0.26 on a PC and
4. our operating environment runs tomcat 5.5.26 on Intel Itanium OpenVMS servers
5. we know that tomcat 5.5.26 on Itanium OpenVMS is old but HP provides nothing any better
6. HP has developed this tomcat to be a fast one,
hence a lot of shareable images,
hence not a pure java solution,
hence more of a native port - to what degree is unknown to us
7. We run our apps on
JDK 1.6.0-33 on PC and
JDK 1.6.0-2.p1 on OpenVMS
HP again is not yet able to deliver an OpenJDK-7
and we don't have any clue, even asking many times, about the road-map.
so upgrading is limitted
8. we use apache axis2-1.6.1 on tomcat OpenVMS 5.5.26 / java 1.6.0-2.p1
regarding upgrading to java 1.7 (7.0)
Ubuntu axis2-1.7.0 from trunk does not even build so far using java-7-oracle
so I had to downgrade to java-6-oracle for a clean axis2 trunk build on Ubuntu (at home)!
regarding upgrading to java 1.7 - yes - as soon as apache-axis2 is that far.
this - as we have to endorse certain jar files
both JRE/lib/endorsed and tomcat/common/lib/endorsed
with jars from jdk-7 to make axis2-JAXWS used annotation classes run
9. we have a rather complex environment
10. log4j-1.2.16.jar is used at
DKA3:[APACHE.JAKARTA.TOMCAT.common.lib]
and log4j-1.2.15.jar (my oversight) is used at
DKA3:[APACHE.JAKARTA.TOMCAT.webapps.axis2.WEB-INF.lib]
and log4j-1.2.16.jar is used at
DKA3:[APACHE.JAKARTA.TOMCAT.WEBAPPS.spezplafs.web-inf.lib]
11. to answer your question: " Are you writing all of your output to console? "
no we do not write all output only to consol but to various log files as well
12. TOMCAT LOGGING is defined by DKA3:[APACHE.JAKARTA.TOMCAT.common.classes]log4j.properties
Note: they are not finalized yet, the ConversionPattern will be harmonized to %d [%-5p] <%t> %c (%F:%L) %m%n
[log4j.properties inline begin]
log4j.debug=true
# -------------------------------------------------------------------
# Copyright 2001-2004 The Apache Software Foundation.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# -------------------------------------------------------------------
log4j.rootLogger=DEBUG, CONSOLE
# in absence of a true TC_CONSole - the log goes into
# apache$specific:[000000]APACHE$JAKARTA_SERVER_OUTPUT.LOG
# -------------------------------------------------------------------
# CONSOLE is set to be a ConsoleAppender using a PatternLayout. -----
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d %-5p %c - %m%n
log4j.appender.CONSOLE.Threshold=INFO
# -------------------------------------------------------------------
#- Set your loggers priority to what you need -----------------------
# Logger logging WHAT it logs WHO is actually logging
log4j.logger.org.apache.catalina=INFO, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.org.apache.catalina.HostConfig=DEBUG, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.org.apache.coyote=INFO, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.org.apache.jasper=INFO, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.org.apache.jk=INFO, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.org.apache.tomcat=INFO, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.org.apache.commons=INFO, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.de.hunsicker.jalopy.io=FATAL, TC_FAP, CONSOLE, TC_CHAINSAW
log4j.logger.httpclient.wire.header=FATAL, TC_FAP, CONSOLE, TC_CHAINSAW
# -------------------------------------------------------------------
# define the additivities used to prevent logging twice the same msg
# NOTE: each logger needs an additivity set or you risk logging twice
#
log4j.additivity.org.apache.catalina=false
log4j.additivity.org.apache.catalina.HostConfig=false
log4j.additivity.org.apache.coyote=false
log4j.additivity.org.apache.jasper=false
log4j.additivity.org.apache.jk=false
log4j.additivity.org.apache.tomcat=false
log4j.additivity.org.apache.commons=false
# -------------------------------------------------------------------
# TC_CONS is set to be a ConsoleAppender using a PatternLayout. -----
log4j.appender.TC_CONS=org.apache.log4j.ConsoleAppender
log4j.appender.TC_CONS.layout=org.apache.log4j.PatternLayout
log4j.appender.TC_CONS.layout.ConversionPattern=%d %-5p %c - %m%n
log4j.appender.TC_CONS.Threshold=INFO
# -------------------------------------------------------------------
# TC_ROLF is a rolling file appender --- not used yet / no need to parse
log4j.appender.TC_ROLF=org.apache.log4j.RollingFileAppender
log4j.appender.TC_ROLF.Append=true
log4j.appender.TC_ROLF.File=/tmlog/tomcat_rolf.log
log4j.appender.TC_ROLF.MaxFileSize=2MB
log4j.appender.TC_ROLF.MaxBackupIndex=10
log4j.appender.TC_ROLF.layout=org.apache.log4j.PatternLayout
log4j.appender.TC_ROLF.layout.ConversionPattern=%p %t %c - %m%n
# -------------------------------------------------------------------
# TC_FAP is set to be a File appender using a PatternLayout. -------
log4j.appender.TC_FAP=org.apache.log4j.FileAppender
log4j.appender.TC_FAP.File=/tmlog/tomcat_fap.log
log4j.appender.TC_FAP.Append=true
log4j.appender.TC_FAP.layout=org.apache.log4j.PatternLayout
log4j.appender.TC_FAP.layout.ConversionPattern=%-5p - %m%n
# -------------------------------------------------------------------
# TC_CHAINSAW is an appender sending to a remote host GUI -------
# feeding the TC_CHAINSAW client listening on TCP/IP port 4449
log4j.appender.TC_CHAINSAW=org.apache.log4j.net.SocketHubAppender
log4j.appender.TC_CHAINSAW.Port=4449
log4j.appender.TC_CHAINSAW.LocationInfo=true
IA64-2>
12. AXIS2-1.6.1 LOGGING is defined by DKA3:[APACHE.JAKARTA.TOMCAT.webapps.axis2.WEB-INF.classes]log4j.properties
Note: ConversionPattern will be harmonized to %d [%-5p] <%t> %c (%F:%L) %m%n
AX_FAP appender is used as template for programmatic establishment of a user-session-specific log4j.logging
(to keep a user session log for each session the user has with its long lasting web service proving object)
IA64-2>type log4j.properties
log4j.debug=true
# -------------------------------------------------------------------
# Copyright 2001-2004 The Apache Software Foundation.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# -------------------------------------------------------------------
#***************** AXIS2 PART ***************************************
log4j.rootLogger=DEBUG, CONSOLE
#
# -------------------------------------------------------------------
# CONSOLE is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=%d %-5p %c - %m%n
log4j.appender.CONSOLE.Threshold=INFO
# -------------------------------------------------------------------
#- Set your loggers priority to what you need -----------------------
# Logger logging WHAT it logs WHO is actually logging
log4j.logger.org.apache.axiom=WARN, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW
log4j.logger.org.apache.axis2=INFO, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW
log4j.logger.org.apache.axis2.deployment=DEBUG, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW
log4j.logger.org.apache.axis2.enterprise=INFO, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW
# -------------------------------------------------------------------
log4j.additivity.org.apache.axiom=false
log4j.additivity.org.apache.axis2=false
log4j.additivity.org.apache.axis2.deployment=false
log4j.additivity.org.apache.axis2.enterprise=false
# -------------------------------------------------------------------
# AX_CONS is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.AX_CONS=org.apache.log4j.ConsoleAppender
log4j.appender.AX_CONS.layout=org.apache.log4j.PatternLayout
log4j.appender.AX_CONS.layout.ConversionPattern=[%-5p] %m%n
#log4j.appender.AX_CONS.layout.ConversionPattern=%d %-5p %c - %m%n
log4j.appender.AX_CONS.Threshold=INFO
#
# -------------------------------------------------------------------
# AX_FAP is set to be a File appender using a PatternLayout. -------
log4j.appender.AX_FAP=org.apache.log4j.FileAppender
log4j.appender.AX_FAP.File=/axlog/axis2_SpServer.log
log4j.appender.AX_FAP.Append=false
log4j.appender.AX_FAP.layout=org.apache.log4j.PatternLayout
log4j.appender.AX_FAP.layout.ConversionPattern=[%-5p] - %m%n
log4j.appender.AX_CONS.Threshold=INFO
#
# -------------------------------------------------------------------
# AX_ROLF is a rolling file appender --- not used yet / no need to parse
log4j.appender.AX_ROLF=org.apache.log4j.RollingFileAppender
log4j.appender.AX_ROLF.Append=true
log4j.appender.AX_ROLF.File=/axlog/axis2_rolf.log
log4j.appender.AX_ROLF.MaxFileSize=2MB
log4j.appender.AX_ROLF.MaxBackupIndex=10
log4j.appender.AX_ROLF.layout=org.apache.log4j.PatternLayout
log4j.appender.AX_ROLF.layout.ConversionPattern=[%-5p] %t %c - %m%n
log4j.appender.AX_ROLF.Threshold=INFO
#
# -------------------------------------------------------------------
# AX_CHAINSAW is an appender sending to a remote host GUI -------
# feeding the AX_CHAINSAW client listening on TCP/IP port 4450
log4j.appender.AX_CHAINSAW=org.apache.log4j.net.SocketHubAppender
log4j.appender.AX_CHAINSAW.Port=4450
log4j.appender.AX_CHAINSAW.LocationInfo=true
# rule of dumb: each log4j.logger... needs one or more appenders !!!!
#
# -------------------------------------------------------------------
# Set the enterprise logger priority to FATAL
log4j.logger.de.hunsicker.jalopy.io=INFO, CONSOLE
log4j.logger.httpclient.wire.header=INFO, CONSOLE
log4j.logger.org.apache.commons.httpclient=INFO, CONSOLE
# -------------------------------------------------------------------
#- create the SpServer Logger ---------------------------------------
# this is the CONFIGURED logger for the SpServer.java JavaPart
# the Configurator strips of the logger_prefix "log4j.logger."
# the logger is then known in the hierarchy as
# "axawl.spezpla.servers.SpezplaService.SpServer"
# retrive this configured logger from log4j.hierarchy through
# Logger log = Logger.getLogger(SpServer.class);
log4j.logger.com.axa.ch.spezpla.servers.SpezplaService.SpServer=INFO, AX_FAP, AX_CHAINSAW
# -------------------------------------------------------------------
# to prevent that logging events are propagated to parent loggers
# and finally arrive at the root loggers appender, printed to the root-
# loggers files i.e. additivity must be set to false to prevent this.
# please goto http://logging.apache.org/log4j/1.2/manual.html and read
# the short manual or buy the full manual
log4j.additivity.com.axa.ch.spezpla.servers.SpezplaService.SpServer=false
IA64-2>
13. SpezplaFS-1.6.1 LOGGING is defined by DKA3:[APACHE.JAKARTA.TOMCAT.webapps.SpezplaFS.WEB-INF.classes]log4j.properties
Note: ConversionPattern will be harmonized to %d [%-5p] <%t> %c (%F:%L) %m%n
IA64-2>type log4j.properties
log4j.debug=true
#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
#
# Set root category priority to INFO and its only appender to CONSOLE.
log4j.rootCategory=INFO, CONSOLE, LOGFILE
# Set the enterprise logger priority to ERROR
log4j.logger.org.apache.axis2.enterprise=FATAL
log4j.logger.de.hunsicker.jalopy.io=FATAL
log4j.logger.httpclient.wire.header=FATAL
log4j.logger.org.apache.commons.httpclient=FATAL
# CONSOLE is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOL.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
## LOGFILE is set to be a File appender using a PatternLayout.
log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File=/axlog/SpezplaFS_ALL_fap.log
log4j.appender.LOGFILE.Append=true
log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
#log4j.appender.LOGFILE.layout.ConversionPattern=%d [%t] %-5p %c %x - %m%n
#log4j.appender.LOGFILE.layout.ConversionPattern=%d %-5p %c - %m%n
#log4j.appender.CONSOL.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
# -------------------------------------------------------------------
# SpezplaFS Logger is INFO to Appender FS_FAP
#log4j.logger.com.axa.ch.spezpla.fs1=INFO, FS_FAP
#log4j.additivity.com.axa.ch.spezpla.fs1=false
#this logger should not log anything as long as additivity below is false
#
log4j.logger.com.axa.ch.spezpla.fs1.handler.LoggingSOAPHandler=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.handler.LoggingSOAPHandler=false
log4j.logger.com.axa.ch.spezpla.fs1.MtomFilePortImpl=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.MtomFilePortImpl=false
log4j.logger.com.axa.ch.spezpla.fs1.MtomFile12PortImpl=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.MtomFile12PortImpl=false
log4j.logger.com.axa.ch.spezpla.fs1.SendImage=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.SendImage=false
log4j.logger.com.axa.ch.spezpla.fs1.SendImageResponse=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.SendImageResponse=false
log4j.logger.com.axa.ch.spezpla.fs1.DownloadImage=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.DownloadImage=false
log4j.logger.com.axa.ch.spezpla.fs1.DownloadImageResponse=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.DownloadImageResponse=false
log4j.logger.com.axa.ch.spezpla.fs1.UploadImage=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.UploadImage=false
log4j.logger.com.axa.ch.spezpla.fs1.UploadImageResponse=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.UploadImageResponse=false
log4j.logger.com.axa.ch.spezpla.fs1.ImageDepot=DEBUG, FS_FAP
log4j.additivity.com.axa.ch.spezpla.fs1.ImageDepot=false
log4j.logger.org.apache.axis2.jaxws.runtime.description.marshal.impl.ArtifactProcessor=DEBUG, FS_DBG
log4j.additivity.org.apache.axis2.jaxws.runtime.description.marshal.impl.ArtifactProcessor=false
log4j.logger.org.apache.axis2.jaxws.runtime.description.marshal.impl.AnnotationBuilder=DEBUG, FS_DBG
log4j.additivity.org.apache.axis2.jaxws.runtime.description.marshal.impl.AnnotationBuilder=false
log4j.logger.org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder=DEBUG, FS_DBG
log4j.additivity.org.apache.axis2.jaxws.runtime.description.marshal.impl.MarshalServiceRuntimeDescriptionBuilder=false
log4j.logger.org.apache.axis2.jaxws.runtime.description.marshal.impl.PropertyDescriptorMapBuilder=DEBUG, CONSOLE, FS_DBG
log4j.additivity.org.apache.axis2.jaxws.runtime.description.marshal.impl.PropertyDescriptorMapBuilder=false
# SpezplaFS Appender
log4j.appender.FS_FAP=org.apache.log4j.FileAppender
log4j.appender.FS_FAP.File=/axlog/SpezplaFS_LoggingSOAPHandler_fap.log
log4j.appender.FS_FAP.Append=false
log4j.appender.FS_FAP.layout=org.apache.log4j.PatternLayout
log4j.appender.FS_FAP.layout.ConversionPattern=%-5p - %-50c- %m%n
log4j.appender.FS_DBG=org.apache.log4j.FileAppender
log4j.appender.FS_DBG.File=/axlog/Spezpla_FS_DBG.log
log4j.appender.FS_DBG.Append=false
log4j.appender.FS_DBG.layout=org.apache.log4j.PatternLayout
log4j.appender.FS_DBG.layout.ConversionPattern=%-5p - %-50c- %m%n
#log4j.appender.FS_FAP.layout.ConversionPattern=%-5p - %d - %t - %c - %m%n
#log4j.appender.FS_FAP.layout.ConversionPattern=%d %-5p %c - %m%n
#log4j.appender.FS_FAP.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n
#log4j.appender.FS_FAP.layout.ConversionPattern=%-5p - %d - %m%n
##
log4j.debug=false
IA64-2>
14. apache$specific:[000000]apache$jakarta_server_output.log generated by this log4j.properties is
15. the main apache tomcat sys$output (stdout) from this morning
please note that tomcat log4j.proeprties and axis2 log4j.properties are parsed but not so
for SpezplaFS apps
WHY ?
as I wrote initially - when you declare -Dlog4j.configuration=/path/to/tomcat's/log4j.properties
the whole parsing is a bit different, see your answer +2 from Rainer Jung
IA64-2>apalog
$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
command file invoked: SYS$COMMON:[SYSMGR]APACHE$JAKARTA_CONFIG.COM
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:[000000]
= APACHE$SPECIFIC:[000000]
= APACHE$COMMON:[000000]
P1 = "RUN"
P2 = ""
P3 = ""
P4 = ""
P5 = ""
P6 = ""
P7 = ""
P8 = ""
java_vms_base = INTEG2$DKA3:[000000.JAVA$60.
JAVA_HOME = /INTEG2$DKA3/000000/JAVA$60
SYSTEM_CLASSPATH = INTEG2$DKA3:[000000.JAVA$60.LIB]TOOLS.JAR
Using Java 6.0 setup -- $ @sys$manager:java$60_setup
Running Tomcat.....
0: integ2$dka3:[000000.java$60.bin]java$java.exe;1
1: -Djava.endorsed.dirs=/disk$oracle2/apache/jakarta/tomcat/common/endorsed
2: -Dcatalina.base=/disk$oracle2/apache/jakarta/tomcat/
3: -Dcatalina.home=/disk$oracle2/apache/jakarta/tomcat/
4: -Dcatalina.tmpdir=/disk$oracle2/apache/jakarta/tomcat/temp
5: org.apache.catalina.startup.Bootstrap
6: start
log4j: Parsing for [root] with value=[DEBUG, CONSOLE].
log4j: Level token is [DEBUG].
log4j: Category root set to DEBUG
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: Setting property [threshold] to [INFO].
log4j: Parsed "CONSOLE" options.
log4j: Parsing for [org.apache.catalina.HostConfig] with value=[DEBUG, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [DEBUG].
log4j: Category org.apache.catalina.HostConfig set to DEBUG
log4j: Parsing appender named "TC_FAP".
log4j: Parsing layout options for "TC_FAP".
log4j: Setting property [conversionPattern] to [%-5p - %m%n].
log4j: End of parsing for "TC_FAP".
log4j: Setting property [append] to [true].
log4j: Setting property [file] to [/tmlog/tomcat_fap.log].
log4j: setFile called: /tmlog/tomcat_fap.log, true
log4j: setFile ended
log4j: Parsed "TC_FAP" options.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Setting property [port] to [4449].
log4j: Setting property [locationInfo] to [true].
log4j: Parsed "TC_CHAINSAW" options.
log4j: Handling log4j.additivity.org.apache.catalina.HostConfig=[false]
log4j: Setting additivity for "org.apache.catalina.HostConfig" to false
log4j: Parsing for [org.apache.jk] with value=[INFO, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.jk set to INFO
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.jk=[false]
log4j: Setting additivity for "org.apache.jk" to false
log4j: Parsing for [org.apache.coyote] with value=[INFO, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.coyote set to INFO
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.coyote=[false]
log4j: Setting additivity for "org.apache.coyote" to false
log4j: Parsing for [org.apache.tomcat] with value=[INFO, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.tomcat set to INFO
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.tomcat=[false]
log4j: Setting additivity for "org.apache.tomcat" to false
log4j: Parsing for [org.apache.catalina] with value=[INFO, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.catalina set to INFO
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE"
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.catalina=[false]
log4j: Setting additivity for "org.apache.catalina" to false
log4j: Parsing for [de.hunsicker.jalopy.io] with value=[FATAL, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [FATAL].
log4j: Category de.hunsicker.jalopy.io set to FATAL
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.de.hunsicker.jalopy.io=[null]
log4j: Parsing for [org.apache.commons] with value=[INFO, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.commons set to INFO
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.commons=[false]
log4j: Setting additivity for "org.apache.commons" to false
log4j: Parsing for [httpclient.wire.header] with value=[FATAL, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [FATAL].
log4j: Category httpclient.wire.header set to FATAL
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.httpclient.wire.header=[null]
log4j: Parsing for [org.apache.jasper] with value=[INFO, TC_FAP, CONSOLE, TC_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.jasper set to INFO
log4j: Parsing appender named "TC_FAP".
log4j: Appender "TC_FAP" was already parsed.
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Parsing appender named "TC_CHAINSAW".
log4j: Appender "TC_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.jasper=[false]
log4j: Setting additivity for "org.apache.jasper" to false
log4j: Finished configuring.
2013-03-27 10:32:23,291 INFO org.apache.coyote.http11.Http11BaseProtocol - Initializing Coyote HTTP/1.1 on http-8080
2013-03-27 10:32:23,307 INFO org.apache.catalina.startup.Catalina - Initialization processed in 1193 ms
2013-03-27 10:32:23,541 INFO org.apache.catalina.core.StandardService - Starting service Catalina
2013-03-27 10:32:23,551 INFO org.apache.catalina.core.StandardEngine - Starting Servlet Engine: Apache Tomcat/5.5.26
2013-03-27 10:32:23,569 INFO org.apache.catalina.core.StandardHost - XML validation disabled
No services directory was found under /disk$oracle2/apache/jakarta/tomcat/webapps/SpezplaFS/WEB-INF.
Mar 27, 2013 10:32:28 AM org.apache.axis2.deployment.util.TempFileManager <clinit>
INFO: TempFileManager::unable to delete /SYS$SCRATCH/axis2-tmp-2066484910635477958.tmp
Mar 27, 2013 10:32:28 AM org.apache.axis2.deployment.util.TempFileManager <clinit>
INFO: TempFileManager::unable to delete /SYS$SCRATCH/axis2-tmp-8485571262211535436.tmp
Deploying module: addressing-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/SpezplaFS/WEB-INF/modules/addressing-1.6.1.mar
Deploying module: addressing-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/SpezplaFS/WEB-INF/lib/addressing-1.6.1.mar
Deploying JAXWS annotated class com.axa.ch.spezpla.fs1.MtomFile12PortImpl as a service - MtomFileService12
Deploying JAXWS annotated class com.axa.ch.spezpla.fs1.MtomFilePortImpl as a service - MtomFileService
2013-03-27 10:32:36,167 INFO org.apache.catalina.startup.HostConfig - Deploying web application archive axis2.war
log4j: Parsing for [root] with value=[DEBUG, CONSOLE].
log4j: Level token is [DEBUG].
log4j: Category root set to DEBUG
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: Setting property [threshold] to [INFO].
log4j: Parsed "CONSOLE" options.
log4j: Parsing for [org.apache.axis2.deployment] with value=[DEBUG, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW].
log4j: Level token is [DEBUG].
log4j: Category org.apache.axis2.deployment set to DEBUG
log4j: Parsing appender named "AX_CONS".
log4j: Parsing layout options for "AX_CONS".
log4j: Setting property [conversionPattern] to [[%-5p] %m%n].
log4j: End of parsing for "AX_CONS".
log4j: Setting property [threshold] to [INFO].
log4j: Parsed "AX_CONS" options.
log4j: Parsing appender named "AX_FAP".
log4j: Parsing layout options for "AX_FAP".
log4j: Setting property [conversionPattern] to [[%-5p] - %m%n].
log4j: End of parsing for "AX_FAP".
log4j: Setting property [append] to [false].
log4j: Setting property [file] to [/axlog/axis2_SpServer.log].
log4j: setFile called: /axlog/axis2_SpServer.log, false
log4j: setFile ended
log4j: Parsed "AX_FAP" options.
log4j: Parsing appender named "AX_ROLF".
log4j: Parsing layout options for "AX_ROLF".
log4j: Setting property [conversionPattern] to [[%-5p] %t %c - %m%n ].
log4j: End of parsing for "AX_ROLF".
log4j: Setting property [maxFileSize] to [2MB ].
log4j: Setting property [threshold] to [INFO].
log4j: Setting property [append] to [true].
log4j: Setting property [file] to [/axlog/axis2_rolf.log].
log4j: Setting property [maxBackupIndex] to [10].
log4j: setFile called: /axlog/axis2_rolf.log, true
log4j: setFile ended
log4j: Parsed "AX_ROLF" options.
log4j: Parsing appender named "AX_CHAINSAW".
log4j: Setting property [locationInfo] to [true].
log4j: Setting property [port] to [4450].
log4j: Parsed "AX_CHAINSAW" options.
log4j: Handling log4j.additivity.org.apache.axis2.deployment=[false]
log4j: Setting additivity for "org.apache.axis2.deployment" to false
log4j: Parsing for [com.axa.ch.spezpla.servers.SpezplaService.SpServer] with value=[INFO, AX_FAP, AX_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category com.axa.ch.spezpla.servers.SpezplaService.SpServer set to INFO
log4j: Parsing appender named "AX_FAP".
log4j: Appender "AX_FAP" was already parsed.
log4j: Parsing appender named "AX_CHAINSAW".
log4j: Appender "AX_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.com.axa.ch.spezpla.servers.SpezplaService.SpServer=[false]
log4j: Setting additivity for "com.axa.ch.spezpla.servers.SpezplaService.SpServer" to false
log4j: Parsing for [org.apache.commons.httpclient] with value=[INFO, CONSOLE].
log4j: Level token is [INFO].
log4j: Category org.apache.commons.httpclient set to INFO
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Handling log4j.additivity.org.apache.commons.httpclient=[null]
log4j: Parsing for [org.apache.axiom] with value=[WARN, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW].
log4j: Level token is [WARN].
log4j: Category org.apache.axiom set to WARN
log4j: Parsing appender named "AX_CONS".
log4j: Appender "AX_CONS" was already parsed.
log4j: Parsing appender named "AX_FAP".
log4j: Appender "AX_FAP" was already parsed.
log4j: Parsing appender named "AX_ROLF".
log4j: Appender "AX_ROLF" was already parsed.
log4j: Parsing appender named "AX_CHAINSAW".
log4j: Appender "AX_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.axiom=[false]
log4j: Setting additivity for "org.apache.axiom" to false
log4j: Parsing for [org.apache.axis2.enterprise] with value=[INFO, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.axis2.enterprise set to INFO
log4j: Parsing appender named "AX_CONS".
log4j: Appender "AX_CONS" was already parsed.
log4j: Parsing appender named "AX_FAP".
log4j: Appender "AX_FAP" was already parsed.
log4j: Parsing appender named "AX_ROLF".
log4j: Appender "AX_ROLF" was already parsed.
log4j: Parsing appender named "AX_CHAINSAW".
log4j: Appender "AX_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.axis2.enterprise=[false]
log4j: Setting additivity for "org.apache.axis2.enterprise" to false
log4j: Parsing for [org.apache.axis2] with value=[INFO, AX_CONS, AX_FAP, AX_ROLF, AX_CHAINSAW].
log4j: Level token is [INFO].
log4j: Category org.apache.axis2 set to INFO
log4j: Parsing appender named "AX_CONS".
log4j: Appender "AX_CONS" was already parsed.
log4j: Parsing appender named "AX_FAP".
log4j: Appender "AX_FAP" was already parsed.
log4j: Parsing appender named "AX_ROLF".
log4j: Appender "AX_ROLF" was already parsed.
log4j: Parsing appender named "AX_CHAINSAW".
log4j: Appender "AX_CHAINSAW" was already parsed.
log4j: Handling log4j.additivity.org.apache.axis2=[false]
log4j: Setting additivity for "org.apache.axis2" to false
log4j: Parsing for [de.hunsicker.jalopy.io] with value=[INFO, CONSOLE].
log4j: Level token is [INFO].
log4j: Category de.hunsicker.jalopy.io set to INFO
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Handling log4j.additivity.de.hunsicker.jalopy.io=[null]
log4j: Parsing for [httpclient.wire.header] with value=[INFO, CONSOLE].
log4j: Level token is [INFO].
log4j: Category httpclient.wire.header set to INFO
log4j: Parsing appender named "CONSOLE".
log4j: Appender "CONSOLE" was already parsed.
log4j: Handling log4j.additivity.httpclient.wire.header=[null]
log4j: Finished configuring
[INFO ] Clustering has been disabled
[INFO ] Deploying module: addressing-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/addressing-1.6.1.mar
[INFO ] Deploying module: jaxws-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/axis2-jaxws-mar-1.6.1.mar
[INFO ] Deploying module: metadataExchange-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/mex-1.6.1.mar
[INFO ] Deploying module: mtompolicy-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/mtompolicy-1.6.1.mar
[INFO ] Deploying module: ping-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/ping-1.6.1.mar
[INFO ] Deploying module: script-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/scripting-1.6.1.mar
[INFO ] Deploying module: soapmonitor-1.6.1 - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/modules/soapmonitor-1.6.1.mar
[INFO ] Deploying Web service: SpezplaService-1.6.1.aar - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/services/SpezplaService-1.6.1.aar
[INFO ] Deploying Web service: version-1.6.1.aar - file:/disk$oracle2/apache/jakarta/tomcat/webapps/axis2/WEB-INF/services/version-1.6.1.aar
2013-03-27 10:32:41,643 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/balancer] - org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]
2013-03-27 10:32:42,228 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/jsp-examples] - ContextListener: contextInitialized()
2013-03-27 10:32:42,230 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/jsp-examples] - SessionListener: contextInitialized()
2013-03-27 10:32:43,051 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/servlets-examples] - ContextListener:contextInitialized()
2013-03-27 10:32:43,052 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/servlets-examples] - SessionListener:contextInitialized()
2013-03-27 10:32:43,897 INFO org.apache.coyote.http11.Http11BaseProtocol - Starting Coyote HTTP/1.1 on http-8080
2013-03-27 10:32:44,122 INFO org.apache.jk.common.ChannelSocket - JK: ajp13 listening on /0.0.0.0:8009
2013-03-27 10:32:44,141 INFO org.apache.jk.server.JkMain - Jk running ID=0 time=1/62 config=null
2013-03-27 10:32:44,266 INFO org.apache.catalina.storeconfig.StoreLoader - Find registry server-registry.xml at classpath resource
2013-03-27 10:32:44,507 INFO org.apache.catalina.startup.Catalina - Server startup in 21199 ms
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc2681e1114283bf2ec5167f006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc268199314283bf2ec5164f006beac8731052.log, false
java.lang.NullPointerException
at com.axa.ch.spezpla.servers.SpezplaService.SpServer.fktmap(SpServer.java:882)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:97)
at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:619)
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc26817ded4283bf2ec5165f006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_8bcae84f4efc268199314283bf2ec5164f006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_8bcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_8bcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_bbcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
java.lang.NullPointerException
at com.axa.ch.spezpla.servers.SpezplaService.SpServer.fktmap(SpServer.java:882)
at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:97)
at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:110)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181)
at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:619)
log4j: setFile called: /axlog/axis2_SpServer_bbcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_abcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_8bcae84f4efc26817ded4283bf2ec5165f006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_dbcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc26811dc27583bf2ec516ee006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_abcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_cbcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_fbcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_ebcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_bbcae84f4efc26817ded4283bf2ec5165f006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc2681aff3b583bf2ec516be006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_1bcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_9bcae84f4efc2681aae64483bf2ec5169e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_dbcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_0bcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_abcae84f4efc26817ded4283bf2ec5165f006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_cbcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_fbcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_3bcae84f4efc2681b0672283bf2ec5168e006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_8bcae84f4efc26811dc27583bf2ec516ee006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_ebcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_1bcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_8bcae84f4efc2681aff3b583bf2ec516be006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_0bcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_3bcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
log4j: setFile called: /axlog/axis2_SpServer_2bcae84f4efc2681363c7283bf2ec516ae006beac8731052.log, false
2013-03-27 13:34:22,096 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager] - HTMLManager: init: Associated with Deployer 'Catalina:type=Deployer,host=localhost'
2013-03-27 13:34:22,098 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager] - HTMLManager: init: Global resources are available
2013-03-27 13:34:22,105 INFO org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager] - HTMLManager: list: Listing contexts for virtual host 'localhost'
IA64-2>
16. your output is different
[main] is a thread, and as I wrote above, <%t> will add a thread as <main> where as < > marks it as thread
also %d will be added to ConversionPattern to have a time stamp with each log entry
17. what I do not understand is: I have a SpezplaFS/WEB-INF/classes/log4j.properties above shown
why is it not parsed
18. do you think it is better to put all properties for all applications into one tomcat log4j.properties file
19. how can I make it a watched resource in tomcat 5.5.26 on OpenVMS
many thanks and yes - the in-lines are long :-)
Josef
-----Ursprüngliche Nachricht-----
Von: Mark Eggers [mailto:its_toasted@yahoo.com]
Gesendet: Dienstag, 26. März 2013 18:42
An: users@tomcat.apache.org
Betreff: Re: [tomcat 5.5.26] why are not all log4j.properties files parsed
On 3/26/2013 9:20 AM, Stadelmann Josef wrote:
> we have multiple applications deployed as war files into tomcat webapps.
>
> each apps has its class directory among a lib directory
>
> we use log4j-1.6 and so each web apps/web-inf/classes has its
> log4j.properties file
>
> what we do not understand is the order in which tomcat deployes the
> several web apps and what we do even less understand is in which order
> the various log4j.properties are parsed and used. OR are they just
> parsed and not used, or later used or perhaps used, I tell you "it is
> a mess!"
>
> We can clearly see that it parses
>
> 1. /catalian/lib/log4j.properties
> 2. then it deploys /catalina/webapps/SpezplaFS -
> a. the logging is formatted with rules from
> /catalian/lib/log4j.properties
> b. /SpezplaFS/WEB-INF/classes/log4j.properties is never parsed
> c. but therefore we can see that /catalian/lib/log4j.properties a
> second time
> 3. and our /catalina/webapps/axis2/WEB-INF/classes/log4j.properties
> is never parsed
> a. but as you can see all modules and axis2.war itself is deployed
> b. why is it's own properties file not parsed
> 4. svnkit-dav has not yet its own logging system
>
> any hints welcome
>
> <<log4j-parsing.txt>>
In general, the list strips attachments. Fortunately yours made it through.
It appears that you're using Tomcat 6.0.26 (not 5.5.26) and JRE 1.6.0.30 on a Windows platform.
First order of business - time to upgrade both Tomcat and the JRE.
Second, read the following:
http://tomcat.apache.org/tomcat-6.0-doc/logging.html#Using_Log4j
Third, there is no guaranteed order for deploying web applications.
Fourth - a bit long . . . .
I just ran a quick test, using the log4j.properties file posted in the link I cited above. I found out the following:
The log4j output is different than what you've posted in your attachment. Here's an example of mine:
2013-03-26 10:05:26,889 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying configuration descriptor host-manager.xml
2013-03-26 10:05:27,079 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying configuration descriptor manager.xml
2013-03-26 10:05:27,135 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying web application archive RWeb.war
2013-03-26 10:05:27,841 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying web application directory docs
2013-03-26 10:05:27,862 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying web application directory examples
Here's a portion of yours:
INFO: Deploying web application archive svnkit-dav-1.7.8.war
26.03.2013 16:45:44 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory bck
26.03.2013 16:45:44 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory docs
26.03.2013 16:45:44 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory examples
Are you writing all of your output to console? It might help to post (inline, not as an attachment) your log4j.properties file.
I've word-wrapped and separated the lines. Note that with using the log4j.properties file from the example, I get a [main] in each log entry.
I have one test application (RWeb - demonstrates how to read file-based resources in a web application) that also uses log4j. It's configured with a log4j.xml file in WEB-INF/classes.
Its output is a bit different, and goes to its own file.
2013-03-26 10:05:27,834 INFO
org.mdeggers.rweb.listeners.LogListener.contextInitialized:14 -
Starting application logging
2013-03-26 10:10:57,575 INFO
org.mdeggers.rweb.controllers.CCReader.processRequest:39 -
Getting resources information from a POJO
2013-03-26 10:11:00,540 INFO
org.mdeggers.rweb.controllers.PReader.processRequest:39 -
Getting resources information from a POJO
One of the differences that you can see is that I include the line number in this logging example.
Another thing to try . . . log4j prefers the XML format over the properties format if it sees more than one log4j configuration file. You might try the following:
1. log4j.properties in %CATALINA_HOME%\lib 2. log4j.xml in each WEB-INF\classes
That way you can be sure the log4j.xml file takes precedence for your applications. However, according to the following reference:
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
log4j and its configuration should be read from WEB-INF/lib and WEB-INF/classes before reading from the common classloader.
So, in summary:
1. Put the right information in your subject 2. Upgrade 3. Don't post attachments - add the information inline 4. No, context loading order is not guaranteed or enforced 5. Check your applications' log files to see what format is used 6. Try using XML for your application's log4j configuration (should not
make a difference)
7. Post your Tomcat's log4j.properties file inline if the above doesn't
resolve your issues
8. Tell the list if / when your issues are resolved (and how)
. . . . just my two cents.
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Thank you Rainer
we already observed different behavior in parsing if we do so.
Josef
-----Ursprüngliche Nachricht-----
Von: Rainer Jung [mailto:rainer.jung@kippdata.de]
Gesendet: Mittwoch, 27. März 2013 10:36
An: users@tomcat.apache.org
Betreff: Re: [tomcat 5.5.26] why are not all log4j.properties files parsed
On 26.03.2013 18:42, Mark Eggers wrote:
> 1. Put the right information in your subject 2. Upgrade 3. Don't post
> attachments - add the information inline 4. No, context loading order
> is not guaranteed or enforced 5. Check your applications' log files to
> see what format is used 6. Try using XML for your application's log4j
> configuration (should not
> make a difference)
> 7. Post your Tomcat's log4j.properties file inline if the above doesn't
> resolve your issues
> 8. Tell the list if / when your issues are resolved (and how)
... and check that you are not setting the system property log4j.configuration, because that will overwrite trying to find the config file via the class loader.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Rainer Jung <ra...@kippdata.de>.
On 26.03.2013 18:42, Mark Eggers wrote:
> 1. Put the right information in your subject
> 2. Upgrade
> 3. Don't post attachments - add the information inline
> 4. No, context loading order is not guaranteed or enforced
> 5. Check your applications' log files to see what format is used
> 6. Try using XML for your application's log4j configuration (should not
> make a difference)
> 7. Post your Tomcat's log4j.properties file inline if the above doesn't
> resolve your issues
> 8. Tell the list if / when your issues are resolved (and how)
... and check that you are not setting the system property
log4j.configuration, because that will overwrite trying to find the
config file via the class loader.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Mark Eggers <it...@yahoo.com>.
On 3/26/2013 9:20 AM, Stadelmann Josef wrote:
> we have multiple applications deployed as war files into tomcat webapps.
>
> each apps has its class directory among a lib directory
>
> we use log4j-1.6 and so each web apps/web-inf/classes has its
> log4j.properties file
>
> what we do not understand is the order in which tomcat deployes the
> several web apps and what we do even less understand is in which order
> the various log4j.properties are parsed and used. OR are they just
> parsed and not used, or later used or perhaps used, I tell you "it is a
> mess!"
>
> We can clearly see that it parses
>
> 1. /catalian/lib/log4j.properties
> 2. then it deploys /catalina/webapps/SpezplaFS -
> a. the logging is formatted with rules from
> /catalian/lib/log4j.properties
> b. /SpezplaFS/WEB-INF/classes/log4j.properties is never parsed
> c. but therefore we can see that /catalian/lib/log4j.properties a
> second time
> 3. and our /catalina/webapps/axis2/WEB-INF/classes/log4j.properties
> is never parsed
> a. but as you can see all modules and axis2.war itself is deployed
> b. why is it's own properties file not parsed
> 4. svnkit-dav has not yet its own logging system
>
> any hints welcome
>
> <<log4j-parsing.txt>>
In general, the list strips attachments. Fortunately yours made it through.
It appears that you're using Tomcat 6.0.26 (not 5.5.26) and JRE 1.6.0.30
on a Windows platform.
First order of business - time to upgrade both Tomcat and the JRE.
Second, read the following:
http://tomcat.apache.org/tomcat-6.0-doc/logging.html#Using_Log4j
Third, there is no guaranteed order for deploying web applications.
Fourth - a bit long . . . .
I just ran a quick test, using the log4j.properties file posted in the
link I cited above. I found out the following:
The log4j output is different than what you've posted in your
attachment. Here's an example of mine:
2013-03-26 10:05:26,889 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying configuration descriptor host-manager.xml
2013-03-26 10:05:27,079 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying configuration descriptor manager.xml
2013-03-26 10:05:27,135 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying web application archive RWeb.war
2013-03-26 10:05:27,841 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying web application directory docs
2013-03-26 10:05:27,862 [main] INFO
org.apache.catalina.startup.HostConfig-
Deploying web application directory examples
Here's a portion of yours:
INFO: Deploying web application archive svnkit-dav-1.7.8.war
26.03.2013 16:45:44 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory bck
26.03.2013 16:45:44 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory docs
26.03.2013 16:45:44 org.apache.catalina.startup.HostConfig
deployDirectory
INFO: Deploying web application directory examples
Are you writing all of your output to console? It might help to post
(inline, not as an attachment) your log4j.properties file.
I've word-wrapped and separated the lines. Note that with using the
log4j.properties file from the example, I get a [main] in each log entry.
I have one test application (RWeb - demonstrates how to read file-based
resources in a web application) that also uses log4j. It's configured
with a log4j.xml file in WEB-INF/classes.
Its output is a bit different, and goes to its own file.
2013-03-26 10:05:27,834 INFO
org.mdeggers.rweb.listeners.LogListener.contextInitialized:14 -
Starting application logging
2013-03-26 10:10:57,575 INFO
org.mdeggers.rweb.controllers.CCReader.processRequest:39 -
Getting resources information from a POJO
2013-03-26 10:11:00,540 INFO
org.mdeggers.rweb.controllers.PReader.processRequest:39 -
Getting resources information from a POJO
One of the differences that you can see is that I include the line
number in this logging example.
Another thing to try . . . log4j prefers the XML format over the
properties format if it sees more than one log4j configuration file. You
might try the following:
1. log4j.properties in %CATALINA_HOME%\lib
2. log4j.xml in each WEB-INF\classes
That way you can be sure the log4j.xml file takes precedence for your
applications. However, according to the following reference:
http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
log4j and its configuration should be read from WEB-INF/lib and
WEB-INF/classes before reading from the common classloader.
So, in summary:
1. Put the right information in your subject
2. Upgrade
3. Don't post attachments - add the information inline
4. No, context loading order is not guaranteed or enforced
5. Check your applications' log files to see what format is used
6. Try using XML for your application's log4j configuration (should not
make a difference)
7. Post your Tomcat's log4j.properties file inline if the above doesn't
resolve your issues
8. Tell the list if / when your issues are resolved (and how)
. . . . just my two cents.
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files
parsed
Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
> Subject: AW: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
> are you in fact saying that we can use the latest Tomcat on OpenVMS Itanium 8.4
> given this OpenVMS has yet a oracle/hp java jdk 1.6.0-04 installed?
Yes. I think we would all be extremely surprised (and dismayed) if HP made any changes to Tomcat. They did put a lot of work into the JVM, back in the day.
> any references for that
Direct link from the Tomcat home page:
http://tomcat.apache.org/whichversion.html
Download the .tar or .zip binary distribution and try it.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi Chris
are you in fact saying that we can use the latest Tomcat on OpenVMS Itanium 8.4
given this OpenVMS has yet a oracle/hp java jdk 1.6.0-04 installed?
any references for that
Josef
-----Ursprüngliche Nachricht-----
Von: Christopher Schultz [mailto:chris@christopherschultz.net]
Gesendet: Donnerstag, 28. März 2013 14:11
An: Tomcat Users List
Betreff: Re: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Josef,
On 3/28/13 5:54 AM, Stadelmann Josef wrote:
> -----Ursprüngliche Nachricht----- Von: Christopher Schultz
> [mailto:chris@christopherschultz.net]
>> Yeah, that'll do it: log4j is probably only being initialized once
>> because you have it in a shared location.
>
> may I have to ask HAP - the one who did the OpenVMS port of Tomcat
> the thing is that I've downloaded from a apache archive
> TOMCAT_5_5_26 but it's awfull to build it even on a PC with NetBeans.
Three things:
1. Stop using Tomcat 5.5.x -- it's no longer supported.
2. Tomcat shouldn't need to be "ported" ... if you've got a JVM, it should run without modification.
3. You should not need to "build" Tomcat: just download the binaries and run them -- they are all cross-platform.
>> Right: if you specify [-Dlog4j.configuration], then log4j.properties
>> will be loaded from a specific place. If you don't then
>> log4j.properties will likely be loaded from an arbitrary webapps
>> WEB-INF/classes directory.
>
> but your saying that each webapps needs a log4j for logging and tomcat
> needs one as well !
That is true.
> So for tomcat I put it into /lib on PC and into /common/lib on OpenVMS
> For each apps I put it into /WEB-INF/appsx/classes But what I am
> interested most - where in tomcat code during startup are the log4j
> property files triggered to read
Upgrade, then read:
https://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRVEFIAAoJEBzwKT+lPKRYLGAQAK9fnIvecO9lyj5r8y9hpwao
qVqdKl7JMqMe31Vrw/WcFC6fwZdo6ZT3nTD5vf3GRJiViCYoqmOCr+snBQBa0iD3
I0jk4Iy7dnAIpziqStj9c4lonMHmD64djCml1YeCNQt5t3ApGuw2cZERbcI1VeoX
NpycnOygc2sToJ1C4uQJ17SEjYK4n2Hf2wl55W1VOAopEYrzadgYyOl1iAYZh6k4
Cydrg8hZgo/TVmAa6tG6IDozQDXvYVORwzXFi9wxgZgvKwV8cO5HGC1LpaiXQ9yZ
TQtDncC0dShoJFxfFO9zJ89gPMl9l77Hfqf/R+g0+HbNVYqMPWB5EUYtaJA8YGDz
pOA5dMb2uE/bj28VsRQ3zPiLsx3nxRjUYuu3fdjs/tE1Ka68yMmCdfT653K6y5DO
GlDA+P17CvNwCwhEpq7FXh2TxsCCSzdiYUuqZg4UgGoMjjfifVVlK2HQJ80lRhfJ
ABgvHMksKIGVHB0oqk8X2Jg42LF96sOd09VXbPPFCtBzB4Nmr/w4ShD4BrEi9PY5
SjoLei6bhMZ0s2Q70Vi6e/AWx+qawALuZPw+aN5XTPxcLTtLZhd3O4xwq6nWBf2R
m0T+1eHuBdrvZRh0Wt9ET07fzwy13xyFbp2xVxc03u8MmwLhCIBqoLjgv4ejQ/ne
XCVasrkl0vphIKFW58v6
=hjv+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: AW: AW: [tomcat 5.5.26] why are not all log4j.properties files
parsed
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Josef,
On 3/28/13 5:54 AM, Stadelmann Josef wrote:
> -----Ursprüngliche Nachricht----- Von: Christopher Schultz
> [mailto:chris@christopherschultz.net]
>> Yeah, that'll do it: log4j is probably only being initialized
>> once because you have it in a shared location.
>
> may I have to ask HAP - the one who did the OpenVMS port of Tomcat
> the thing is that I've downloaded from a apache archive
> TOMCAT_5_5_26 but it's awfull to build it even on a PC with
> NetBeans.
Three things:
1. Stop using Tomcat 5.5.x -- it's no longer supported.
2. Tomcat shouldn't need to be "ported" ... if you've got a JVM, it
should run without modification.
3. You should not need to "build" Tomcat: just download the binaries
and run them -- they are all cross-platform.
>> Right: if you specify [-Dlog4j.configuration], then
>> log4j.properties will be loaded from a specific place. If you
>> don't then log4j.properties will likely be loaded from an
>> arbitrary webapps WEB-INF/classes directory.
>
> but your saying that each webapps needs a log4j for logging and
> tomcat needs one as well !
That is true.
> So for tomcat I put it into /lib on PC and into /common/lib on
> OpenVMS For each apps I put it into /WEB-INF/appsx/classes But what
> I am interested most - where in tomcat code during startup are the
> log4j property files triggered to read
Upgrade, then read:
https://tomcat.apache.org/tomcat-7.0-doc/logging.html#Using_Log4j
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRVEFIAAoJEBzwKT+lPKRYLGAQAK9fnIvecO9lyj5r8y9hpwao
qVqdKl7JMqMe31Vrw/WcFC6fwZdo6ZT3nTD5vf3GRJiViCYoqmOCr+snBQBa0iD3
I0jk4Iy7dnAIpziqStj9c4lonMHmD64djCml1YeCNQt5t3ApGuw2cZERbcI1VeoX
NpycnOygc2sToJ1C4uQJ17SEjYK4n2Hf2wl55W1VOAopEYrzadgYyOl1iAYZh6k4
Cydrg8hZgo/TVmAa6tG6IDozQDXvYVORwzXFi9wxgZgvKwV8cO5HGC1LpaiXQ9yZ
TQtDncC0dShoJFxfFO9zJ89gPMl9l77Hfqf/R+g0+HbNVYqMPWB5EUYtaJA8YGDz
pOA5dMb2uE/bj28VsRQ3zPiLsx3nxRjUYuu3fdjs/tE1Ka68yMmCdfT653K6y5DO
GlDA+P17CvNwCwhEpq7FXh2TxsCCSzdiYUuqZg4UgGoMjjfifVVlK2HQJ80lRhfJ
ABgvHMksKIGVHB0oqk8X2Jg42LF96sOd09VXbPPFCtBzB4Nmr/w4ShD4BrEi9PY5
SjoLei6bhMZ0s2Q70Vi6e/AWx+qawALuZPw+aN5XTPxcLTtLZhd3O4xwq6nWBf2R
m0T+1eHuBdrvZRh0Wt9ET07fzwy13xyFbp2xVxc03u8MmwLhCIBqoLjgv4ejQ/ne
XCVasrkl0vphIKFW58v6
=hjv+
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi Chris
my comment+++>>
-----Ursprüngliche Nachricht-----
Von: Christopher Schultz [mailto:chris@christopherschultz.net]
Gesendet: Mittwoch, 27. März 2013 19:35
An: Tomcat Users List
Betreff: Re: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Josef,
On 3/27/13 9:51 AM, Stadelmann Josef wrote:
> -----Ursprüngliche Nachricht----- Von: Christopher Schultz
> [mailto:chris@christopherschultz.net]
>>
>> I highly suspect that you have log4j.jar in either common/lib or
>> shared/lib. In that case, your log4j will initialize only once,
>> probably incorrectly.
>
> +++ this is interessting. IA64-2>dir [.shared] Directory
> DKA3:[APACHE.JAKARTA.TOMCAT.shared] classes.DIR;1 lib.DIR;1
> Total of 2 files. IA64-2>dir [.shared.classes] %DIRECT-W-NOFILES, no
> files found IA64-2>dir [.shared.lib] %DIRECT-W-NOFILES, no files found
> IA64-2>dir Directory DKA3:[APACHE.JAKARTA.TOMCAT.common]
> classes.DIR;1 endorsed.DIR;1 endorsed^.tar.gz;1
> i18n.DIR;1 lib.DIR;1 Total of 5 files. IA64-2>
Oh, crap: you're using VMS. I'm sure VMS is great, but directory listings are just incomprehensible garbage. Versioned files and directories... *eyeroll*...
+++>> if you use unix shell gnv/gnu bash it's not so hard to work with ... :-)
> we use this lib and classes directory in tomcat. it's here in lib
> where log4j.jar is IA64-2>dir [.lib]*log4j* Directory
> DKA3:[APACHE.JAKARTA.TOMCAT.common.lib] log4j-1^.2^.16.jar;1 Total of
> 1 file. IA64-2> +++++
Yeah, that'll do it: log4j is probably only being initialized once because you have it in a shared location.
+++>> may I have to ask HAP - the one who did the OpenVMS port of Tomcat
+++>> the thing is that I've downloaded from a apache archive TOMCAT_5_5_26 but it's awfull to build it even on a PC with NetBeans.
>> If you want to use log4j in each web application, you should put a
>> separate log4j.jar file in each webapp's WEB-INF/lib directory.
>
> +++ we have done that ! there is a minor mismatch as tomcat - the
> oldest dir - has log4j-1.2.15.jarwhile the apps are all at
> log4j.1.2.16.jar
It's not likely to matter.
+++>> that is what I think too.
> +++ note the observed behavior in parsing and later in logging is
> different if we use
> log4j.configuration=/path/to/tomcats/log4j.properties as JVM argument
> from within NetBeans when we start tomcat.
Right: if you specify that, then log4j.properties will be loaded from a specific place. If you don't then log4j.properties will likely be loaded from an arbitrary webapps WEB-INF/classes directory.
+++>> but your saying that each webapps needs a log4j for logging and tomcat needs one as well !
So for tomcat I put it into /lib on PC and into /common/lib on OpenVMS
For each apps I put it into /WEB-INF/appsx/classes
But what I am interested most - where in tomcat code during startup are the log4j property files triggered to read
>> Are you also trying to use log4j for /Tomcat/ logging? If so, you
>> have to do that differently as well. I'm not sure how well it works
>> (or if at all) with Tomcat 5.5.
>
> +++ yes - we really would like to do that
> in example I really need now HostCongig.java's log.debug to print out
> when tomcat lifecycle event does a Reloading Context /axis2 ...
> causing us tremendous troubles at the moment. Maybe we'r hacked
> internally by some security folk.
??!
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRUzvKAAoJEBzwKT+lPKRY/WgQALcyZlbQzixsClMwD7ppyigI
4A1jMfRQGqRI99l7v6qbYfMXjGkI17OMY/TO42avSungIYDxJ0t+VBDgd3DO5WHK
1pPO4XMxhcCdHGGGLwNasB+Z9bbsDsMUam3Sb81z3wVIMV7T+Ag96LEEseVZxJne
TjSE+kmR2d5wQEtk+jHkcB/PZtuY3yt2HZVWSDgW2D08Z0N6eK0wrengFbYzRzwa
pF62hYHWBRlUKGZ0ZrZdsrIkvrtmpjg1espw2G7CqL7dn1vRR5AVLeo2gVuBb8OD
ryMxzY891e1sXWCMerFmpgIXEmeFOruYIAVF3C8IfSEgZZ29PCTQ7kv7VjAvRLhz
gsTkdu1ZbWf4Y/gTqYmjCxZsnl7askjf6vhY8AHkncomqDXdHLjjslW2roGkFvn7
4U7t38iMonKNTgj6iOtotdIwBImdfc+AYTaXStot6V2d5mef/k758VyidCIMNJnA
Xo5SFbt/uAXeG3azTe5llaVKGNdrBt2r0H9D4AbG2lpSyqINU165XCsnbNHjvt79
U+KYOmO9Cu76t1iTnGKTHa4bEemvS7KH2d/8IZCGMaWy0MbvlbLVuhCtTqoOXJZZ
EXDNYLGGm0FR7K4O3M2LZzVdUr2uB85cnaCqjlzbcd6M8g2Oof2YGWbvg73KOz4q
ckv//4/e9bRQLjwYcAEu
=Njwq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Josef,
On 3/27/13 9:51 AM, Stadelmann Josef wrote:
> -----Ursprüngliche Nachricht----- Von: Christopher Schultz
> [mailto:chris@christopherschultz.net]
>>
>> I highly suspect that you have log4j.jar in either common/lib or
>> shared/lib. In that case, your log4j will initialize only once,
>> probably incorrectly.
>
> +++ this is interessting. IA64-2>dir [.shared] Directory
> DKA3:[APACHE.JAKARTA.TOMCAT.shared] classes.DIR;1 lib.DIR;1
> Total of 2 files. IA64-2>dir [.shared.classes] %DIRECT-W-NOFILES,
> no files found IA64-2>dir [.shared.lib] %DIRECT-W-NOFILES, no files
> found IA64-2>dir Directory DKA3:[APACHE.JAKARTA.TOMCAT.common]
> classes.DIR;1 endorsed.DIR;1 endorsed^.tar.gz;1
> i18n.DIR;1 lib.DIR;1 Total of 5 files. IA64-2>
Oh, crap: you're using VMS. I'm sure VMS is great, but directory
listings are just incomprehensible garbage. Versioned files and
directories... *eyeroll*...
> we use this lib and classes directory in tomcat. it's here in lib
> where log4j.jar is IA64-2>dir [.lib]*log4j* Directory
> DKA3:[APACHE.JAKARTA.TOMCAT.common.lib] log4j-1^.2^.16.jar;1 Total
> of 1 file. IA64-2> +++++
Yeah, that'll do it: log4j is probably only being initialized once
because you have it in a shared location.
>> If you want to use log4j in each web application, you should put
>> a separate log4j.jar file in each webapp's WEB-INF/lib
>> directory.
>
> +++ we have done that ! there is a minor mismatch as tomcat - the
> oldest dir - has log4j-1.2.15.jarwhile the apps are all at
> log4j.1.2.16.jar
It's not likely to matter.
> +++ note the observed behavior in parsing and later in logging is
> different if we use
> log4j.configuration=/path/to/tomcats/log4j.properties as JVM
> argument from within NetBeans when we start tomcat.
Right: if you specify that, then log4j.properties will be loaded from
a specific place. If you don't then log4j.properties will likely be
loaded from an arbitrary webapp's WEB-INF/classes directory.
>> Are you also trying to use log4j for /Tomcat/ logging? If so, you
>> have to do that differently as well. I'm not sure how well it
>> works (or if at all) with Tomcat 5.5.
>
> +++ yes - we really would like to do that
> in example I really need now HostCongig.java's log.debug to print
> out when tomcat lifecycle event does a Reloading Context /axis2
> ... causing us tremendous troubles at the moment. Maybe we'r
> hacked internally by some security folk.
??!
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRUzvKAAoJEBzwKT+lPKRY/WgQALcyZlbQzixsClMwD7ppyigI
4A1jMfRQGqRI99l7v6qbYfMXjGkI17OMY/TO42avSungIYDxJ0t+VBDgd3DO5WHK
1pPO4XMxhcCdHGGGLwNasB+Z9bbsDsMUam3Sb81z3wVIMV7T+Ag96LEEseVZxJne
TjSE+kmR2d5wQEtk+jHkcB/PZtuY3yt2HZVWSDgW2D08Z0N6eK0wrengFbYzRzwa
pF62hYHWBRlUKGZ0ZrZdsrIkvrtmpjg1espw2G7CqL7dn1vRR5AVLeo2gVuBb8OD
ryMxzY891e1sXWCMerFmpgIXEmeFOruYIAVF3C8IfSEgZZ29PCTQ7kv7VjAvRLhz
gsTkdu1ZbWf4Y/gTqYmjCxZsnl7askjf6vhY8AHkncomqDXdHLjjslW2roGkFvn7
4U7t38iMonKNTgj6iOtotdIwBImdfc+AYTaXStot6V2d5mef/k758VyidCIMNJnA
Xo5SFbt/uAXeG3azTe5llaVKGNdrBt2r0H9D4AbG2lpSyqINU165XCsnbNHjvt79
U+KYOmO9Cu76t1iTnGKTHa4bEemvS7KH2d/8IZCGMaWy0MbvlbLVuhCtTqoOXJZZ
EXDNYLGGm0FR7K4O3M2LZzVdUr2uB85cnaCqjlzbcd6M8g2Oof2YGWbvg73KOz4q
ckv//4/e9bRQLjwYcAEu
=Njwq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
AW: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
Hi Christopher
my comment +++
-----Ursprüngliche Nachricht-----
Von: Christopher Schultz [mailto:chris@christopherschultz.net]
Gesendet: Dienstag, 26. März 2013 21:19
An: Tomcat Users List
Betreff: Re: [tomcat 5.5.26] why are not all log4j.properties files parsed
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Josef,
On 3/26/13 12:20 PM, Stadelmann Josef wrote:
> we have multiple applications deployed as war files into tomcat
> webapps.
>
> each apps has its class directory among a lib directory
Can you explain that in more detail? I do not understand...
+++ your rigth, my real stupid expression, sorry!
> we use log4j-1.2.16 and so each web apps/web-inf/classes has its
> log4j.properties file
>
> what we do not understand is the order in which tomcat deployes the
> several web apps and what we do even less understand is in which order
> the various log4j.properties are parsed and used. OR are they just
> parsed and not used, or later used orperhapsused, I tell you "it is a
> mess!"
I highly suspect that you have log4j.jar in either common/lib or shared/lib. In that case, your log4j will initialize only once, probably incorrectly.
+++ this is interessting.
IA64-2>dir [.shared]
Directory DKA3:[APACHE.JAKARTA.TOMCAT.shared]
classes.DIR;1 lib.DIR;1
Total of 2 files.
IA64-2>dir [.shared.classes]
%DIRECT-W-NOFILES, no files found
IA64-2>dir [.shared.lib]
%DIRECT-W-NOFILES, no files found
IA64-2>dir
Directory DKA3:[APACHE.JAKARTA.TOMCAT.common]
classes.DIR;1 endorsed.DIR;1 endorsed^.tar.gz;1 i18n.DIR;1 lib.DIR;1
Total of 5 files.
IA64-2>
we use this lib and classes directory in tomcat. it's here in lib where log4j.jar is
IA64-2>dir [.lib]*log4j*
Directory DKA3:[APACHE.JAKARTA.TOMCAT.common.lib]
log4j-1^.2^.16.jar;1
Total of 1 file.
IA64-2> +++++
If you want to use log4j in each web application, you should put a separate log4j.jar file in each webapp's WEB-INF/lib directory.
+++ we have done that ! there is a minor mismatch as tomcat - the oldest dir - has log4j-1.2.15.jar
while the apps are all at log4j.1.2.16.jar
+++ note the observed behavior in parsing and later in logging is different if we use log4j.configuration=/path/to/tomcats/log4j.properties as JVM argument from within NetBeans when we start tomcat.
Are you also trying to use log4j for /Tomcat/ logging? If so, you have to do that differently as well. I'm not sure how well it works (or if at all) with Tomcat 5.5.
+++ yes - we really would like to do that;
in example I really need now HostCongig.java's log.debug to print out when tomcat lifecycle event does a Reloading Context /axis2 ... causing us tremendous troubles at the moment. Maybe we'r hacked internally by some security folk.
As you can see in my previous answer, there is a large apache$jakarta_server_output.log and you can see there that log4j.properties from DKA3:[APACHE.JAKARTA.TOMCAT.common.lib] is parsed., well thanks to CHAINSAW, I have found out all the various active loggers of tomcat; I can say, it works. So it is up to us to define proper appenders for various loggers doing debug output which will other whise not do any logging. also we need it on a one to one basis because just turning on debug-logging fro tomcat is a clear no-go in production, but other loggers like those from HostConfig.java are real helpful in case of troubles.
Thank you Chris
Josef
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRUgLIAAoJEBzwKT+lPKRYPnQQAMjBdaIFPAbhylE+yPL3aAsQ
RnVWf6sUOQuj+UeJaV+s4jREK9nbwgNaLYskceJZnI+CxsFU7/KhmWdEh4E3PbNA
zh+Iy2Q+3bI2S8SPUBCZEn3CKCMcgUIxcgaPO/IAUeQR0ua6IIF88oBBWmGA2hrq
ibFeACROTHeW+yiixC/nh+5d5RJm3lGwpIoh536D/eugKOY/zEge7XYBoIw3X0YY
j8vz9FDOSmjfAVAr90KskSazIcP1LHOqRhv88RS66gFS1UOWUHuPrFnSqjEy0MeK
OQiyjwl2JhQ0A0wj977kcB7Z/C6O3kCedoHzxJjzwIwcOAuqS+t/i5tE4oAYYPbv
Cnpzoy79E0UszHKoy/ZCC+3XJsB/2Kpg5d5CGjqjICVcicZqCD5Vnu8MUs24+oMp
TQMyXzoB9Wluw5U2v161SFpvoEgByXaG1ibvQ3uk9kRdqMDekN+hhrVpIviNb+/+
AbbrtZWV2ssJIGib7B7UI+v8BxbFkKbXZDJ5AYu7gb+sove5qeCZDN2MlZrbmQfl
+mup3PIX+G8i1Hnl5c92xLVirrEnfumzWjMZ9wbxMeXhk65AkH9zyNiV6EaJ68LE
7OlC7+/BpiPn7sUAvxYwnVk7YOyOx2XvvsBkbzVrjclgp4fW16pH/pQPPAGhJVWY
61drrtfdiLuTJP1w8tiY
=yMAk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [tomcat 5.5.26] why are not all log4j.properties files parsed
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Josef,
On 3/26/13 12:20 PM, Stadelmann Josef wrote:
> we have multiple applications deployed as war files into tomcat
> webapps.
>
> each apps has its class directory among a lib directory
Can you explain that in more detail? I do not understand...
> we use log4j-1.6 and so each web apps/web-inf/classes has its
> log4j.properties file
>
> what we do not understand is the order in which tomcat deployes
> the several web apps and what we do even less understand is in
> which order the various log4j.properties are parsed and used. OR
> are they just parsed and not used, or later used orperhapsused, I
> tell you "it is a mess!"
I highly suspect that you have log4j.jar in either common/lib or
shared/lib. In that case, your log4j will initialize only once,
probably incorrectly.
If you want to use log4j in each web application, you should put a
separate log4j.jar file in each webapp's WEB-INF/lib directory.
Are you also trying to use log4j for /Tomcat/ logging? If so, you have
to do that differently as well. I'm not sure how well it works (or if
at all) with Tomcat 5.5.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJRUgLIAAoJEBzwKT+lPKRYPnQQAMjBdaIFPAbhylE+yPL3aAsQ
RnVWf6sUOQuj+UeJaV+s4jREK9nbwgNaLYskceJZnI+CxsFU7/KhmWdEh4E3PbNA
zh+Iy2Q+3bI2S8SPUBCZEn3CKCMcgUIxcgaPO/IAUeQR0ua6IIF88oBBWmGA2hrq
ibFeACROTHeW+yiixC/nh+5d5RJm3lGwpIoh536D/eugKOY/zEge7XYBoIw3X0YY
j8vz9FDOSmjfAVAr90KskSazIcP1LHOqRhv88RS66gFS1UOWUHuPrFnSqjEy0MeK
OQiyjwl2JhQ0A0wj977kcB7Z/C6O3kCedoHzxJjzwIwcOAuqS+t/i5tE4oAYYPbv
Cnpzoy79E0UszHKoy/ZCC+3XJsB/2Kpg5d5CGjqjICVcicZqCD5Vnu8MUs24+oMp
TQMyXzoB9Wluw5U2v161SFpvoEgByXaG1ibvQ3uk9kRdqMDekN+hhrVpIviNb+/+
AbbrtZWV2ssJIGib7B7UI+v8BxbFkKbXZDJ5AYu7gb+sove5qeCZDN2MlZrbmQfl
+mup3PIX+G8i1Hnl5c92xLVirrEnfumzWjMZ9wbxMeXhk65AkH9zyNiV6EaJ68LE
7OlC7+/BpiPn7sUAvxYwnVk7YOyOx2XvvsBkbzVrjclgp4fW16pH/pQPPAGhJVWY
61drrtfdiLuTJP1w8tiY
=yMAk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org