The following highlight possible tools and techniques you might use in troubleshooting errors with Axis2 or Axis 1.4 web services, but is not an exhaustive list. Also, the tools available to you may vary by platform and application server environment.
When trying to understand why a service has failed the following should be considered:
# Set root category log4j.rootCategory=DEBUG, CONSOLE, LOGFILE # Set the enterprise logger priority to FATAL 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.CONSOLE.layout.ConversionPattern=[%p] %m%n # LOGFILE is set to be a File appender using a PatternLayout. log4j.appender.LOGFILE=org.apache.log4j.FileAppender log4j.appender.LOGFILE.File=c:/temp/axis2.log log4j.appender.LOGFILE.Append=true log4j.appender.LOGFILE.layout=org.apache.log4j.PatternLayout log4j.appender.LOGFILE.layout.ConversionPattern= %d [%t] %-5p %c %x - %m%n
You need to place the log4j.properties somewhere in the classpath of the Axis2 or Axis 1.4 WAR file.