Project

General

Profile

Bug #635

IrisWSLog4jInit configuration filename creation should conform with WSS code

Added by Mike Stults almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Mike Stults
Target version:
1.1.9
Start date:
11/14/2014
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

IrisWSLog4jInit appears to vary slightly from WSS when creating a name for getting the log4j properties. This can probably be fixed easily by using the WebUtils.getConfigFileBase utility as in SingletonWrapper in WSS.

History

#1 Updated by Mike Stults almost 10 years ago

Updated IrisWSSLog4jInit to version 0.95, copied method getConfigFileBase to be consistent with WSS, deployed to Nexus, updated WSS pom.

#2 Updated by Mike Stults almost 10 years ago

  • Target version set to 1.1.9

#3 Updated by Robert Weekly almost 10 years ago

Confirmed the new messages in catalina.out log file (below). No changes encountered as end-user.

Recommend that bug be closed.

Dec 03, 2014 11:02:29 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive /Users/rtweekly/apache_tomcat/apache-tomcat-7.0.54/webapps/fdsnws#dataselect#1.war
Info, Log4jInit, property wssConfigDir: /Users/rtweekly/apache_tomcat/config
Info, Log4jInit, prior filename: dataselect-1-log4j.properties
Info, Log4jInit, filename: dataselect-1-log4j.properties
Info, Log4jInit, contextPath: /fdsnws/dataselect/1  log4j file: /Users/rtweekly/apache_tomcat/config/dataselect-1-log4j.properties

#4 Updated by Robert Weekly almost 10 years ago

  • Resolution set to Fixed
  • Status changed from New to Closed

Closed.

Also available in: Atom PDF