Resolution: No Longer Reproducible
Affects Version/s: 7.1.10 DXP FP17, 7.1.X, 7.2.10 DXP FP4, 7.2.X, 7.3.1 CE GA2
Component/s: Portal Configuration > System Settings
Sprint:U&SM| S03 Sprint 24 |5.26-6.9, U&SM| S03 Sprint 25 | 6.9-23, U&SM| S03 Sprint 26 | 6.23-7.7
Steps to reproduce:
- Start Portal
- While Portal is running, create an osgi configuration file WITHOUT property type marker characters and place it within <liferay home>/osgi/config
For example, deploy com.liferay.portal.search.elasticsearch7.configuration.ElasticsearchConnectionConfiguration-test.config with the following properties:
Do not use the type marker, e.g. don't use: active=B"true"
Alternatively, simply change the value of an existing file osgi configuration file while also removing the type markers.
Actual result: After the configurations are processed, the properties within the file are reformatted to invalid syntax where spaces are added and quotes are removed. Example:
I verified that this is happening for other osgi config files as well. This can lead to issues when Portal is restarted since the properties can't be read properly. For example with the config file used above, errors are thrown on startup and the connection that was present in Portal before shut down would no longer be available.
Note: This is not reproducible if the type markers are present. However, in our customer documentation it's communicated that these markers are for informational purposes only and shouldn't be required for proper deployment.
Portal master git commit: 51b0c2844b2c29a02abfcdeb0fa2f02d3300f72f
Portal 7.2.x git commit: 6cd777fe26cc1cc88240ae6a7194a6d32b41a5b5
Not reproducible on:
Portal 7.1.x git commit: c5fe0bfcf2e04d89e70c8fe2e8214cd5f7f65f85