Skip to content

Reduce verbose logging for property file search #3

@stain

Description

@stain

On startup, there is quite a verbose log output from loading of property files and data sources, which can be misleading as it seems like an error:

nable to find /opt/ims/log4j.properties in local Directory
Loaded file log4j.properties using BRIDGEDB_CONFIG from /opt/ims/conf/BridgeDb/log4j.properties
Looking for BridgeDb.properties
Unable to find /opt/ims/BridgeDb.properties in local Directory
No file BridgeDb.properties found in BRIDGEDB_CONFIG directory /opt/ims/conf/BridgeDb
No directory /conf/BridgeDb found in $CATALINA_HOME directory /usr/share/apache-tomcat-7
No directory found at: ../conf/BridgeDb at /opt/ims/../conf/BridgeDb
Loaded BridgeDb.properties from file:/opt/ims/work/Catalina/localhost/QueryExpander/loader/BridgeDb.properties with class loader.
Looking for local.properties
Unable to find /opt/ims/local.properties in local Directory
Loaded file local.properties using BRIDGEDB_CONFIG from /opt/ims/conf/BridgeDb/local.properties
Looking for DataSource.ttl
Unable to find /opt/ims/DataSource.ttl in local Directory
No file DataSource.ttl found in BRIDGEDB_CONFIG directory /opt/ims/conf/BridgeDb
No directory /conf/BridgeDb found in $CATALINA_HOME directory /usr/share/apache-tomcat-7

Perhaps this search path for properties could be reduced, or at least prefix such logging with "DEBUG" rather than look like an error?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions