nextgenhealthcare / connect

The swiss army knife of healthcare integration.
Other
874 stars 267 forks source link

dir.logs in preferences does not have any effect #5428

Open kairos-norbert opened 1 year ago

kairos-norbert commented 1 year ago

Hi all,

entering a different directory for log files in preferences file does not have any effect. The log directory is always created and used in the installation directory. I changed the log directory during installation in the installer dialog, and it's entered correctly in preferences.

dir.appdata works fine.

Using Mirth 4.1.1 under Win10, OpenJDK 11.0.12

# install4j response file for Mirth Connect 4.1.1.b303
dir.appdata=C\:\\Developers\\Projects\\Mirth 4\\appdata
dir.logs=C\:\\Developers\\Projects\\Mirth 4\\logs
pacmano1 commented 1 year ago

Trivial to replicate also, nice catch.

is-simon commented 1 year ago

As a workaround, you can set the log4j2.properties yourself afterwards and use a property:

# sample properties to initialize log4j
rootLogger = ERROR,stdout,fout

# stdout appender
appender.console.type = Console
appender.console.name = stdout
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = %-5p %d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %c: %m%n

# file appender
property.dir.logs = C:/Developers/Projects/Mirth 4/logs
appender.rolling.type = RollingFile
appender.rolling.name = fout
appender.rolling.fileName = ${dir.logs}/mirth.log
appender.rolling.filePattern = ${dir.logs}/mirth.log.%i
appender.rolling.policies.type = Policies
appender.rolling.policies.size.type = SizeBasedTriggeringPolicy
appender.rolling.policies.size.size = 500KB
appender.rolling.strategy.type = DefaultRolloverStrategy
appender.rolling.strategy.max = 20
appender.rolling.layout.type = PatternLayout
appender.rolling.layout.pattern = %-5p %d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %c: %m%n

# splash screen
logger.mirth.name = com.mirth.connect.server.Mirth
logger.mirth.level = INFO

# Mirth Connect server logging
logger.donkeyEngineController.name = com.mirth.connect.server.controllers.DonkeyEngineController
logger.donkeyEngineController.level = INFO
logger.recoveryTask.name = com.mirth.connect.donkey.server.channel.RecoveryTask
logger.recoveryTask.level = INFO
logger.fileReceiver.name = com.mirth.connect.connectors.file.FileReceiver
logger.fileReceiver.level = WARN

# Mirth Connect channel logging
logger.transformer.name = transformer
logger.transformer.level = DEBUG
logger.preprocessor.name = preprocessor
logger.preprocessor.level = DEBUG
logger.postprocessor.name = postprocessor
logger.postprocessor.level = DEBUG
logger.deploy.name = deploy
logger.deploy.level = DEBUG
logger.undeploy.name = undeploy
logger.undeploy.level = DEBUG
logger.filter.name = filter
logger.filter.level = DEBUG
logger.db-connector.name = db-connector
logger.db-connector.level = DEBUG
logger.js-connector.name = js-connector
logger.js-connector.level = DEBUG
logger.attachment.name = attachment
logger.attachment.level = DEBUG
logger.batch.name = batch
logger.batch.level = DEBUG
logger.response.name = response
logger.response.level = DEBUG
logger.shutdown.name = shutdown
logger.shutdown.level = DEBUG

# SQL Logging
logger.sql.name = java.sql
logger.sql.level = ERROR
yadkhoo commented 6 months ago

I have the same problem with 4.4.2.b326 & OpenJDK 11.0.21 windows server 2016.