LibreClinica is the community driven successor of OpenClinica. It is an open source clinical trial software for Electronic Data Capture (EDC) Clinical Data Management (CDM).
Background:
When installing LibreClinica according to the instructions a datainfo.properties file populated with placeholders is used as a template.
Description:
Placeholders in some but not all configuration keys prevent LibreClinica to start properly, even if these keys are not relevant to the configuration of the respective instance. The log message is not descriptive: "One or more listeners failed to start. Full details will be found in the appropriate container log file", "Context [/libreclinica] startup failed due to previous errors".
1) Keys prone to this problem include
Mail configuration
some but not all keys (mailHost e.g. is not critical)
1) Quartz Scheduler Configuration
Setting any of the 3 keys to a placeholders prevents the app from
starting correctly.
A datainfo.properties file where I tried to leave many placeholders, and that still works is attached to this issue.
Expected behaviour:
A log message pointing to the key or at the datainfo.properties file as the source of trouble.
Background:
When installing LibreClinica according to the instructions a datainfo.properties file populated with placeholders is used as a template.
Description:
Placeholders in some but not all configuration keys prevent LibreClinica to start properly, even if these keys are not relevant to the configuration of the respective instance. The log message is not descriptive: "One or more listeners failed to start. Full details will be found in the appropriate container log file", "Context [/libreclinica] startup failed due to previous errors".
1) Keys prone to this problem include
Mail configuration some but not all keys (mailHost e.g. is not critical)
1) Quartz Scheduler Configuration Setting any of the 3 keys to a placeholders prevents the app from starting correctly.
A datainfo.properties file where I tried to leave many placeholders, and that still works is attached to this issue.
Expected behaviour:
A log message pointing to the key or at the datainfo.properties file as the source of trouble.