InvocationTargetException occurs during Liferay startup if there is a subfolder in osgi\configs

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.2.10 DXP FP5, 7.2.X, Master
• Fix Version/s: 7.2.10 DXP FP6, 7.2.X, 7.3.3 CE GA4, 7.3.10 DXP GA1, Master
• Component/s: Core Infrastructure, Portal Configuration
• Labels:
  • ee-ts
  • liferay-fixpack-dxp-6-7210
• Branch Version/s:
  7.2.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/9129

This issue affects master and 7.2 only.

Steps to reproduce:

1. Take a vanilla bundle
2. Add a subfolder under osgi\configs
3. Start Liferay

Actual behavior: Liferay does not start up. InvocationTargetException errors appera in the console. This used to work in DXP 7.1.
Expected behavior: Liferay starts up without exceptions.

Additional information:
Since Liferay 7.2 (it still works in 7.1) it is not possible to have subdirectories in the $LIFERAY_HOME/osgi/configs folder. This removes the possibility to mount the folder from a Kubernetes ConfigMap as this automatically adds a subfolder named "..YYYY_MM_DD_HH_mm_ss.mmmmmmm" with the mounting timestamp and a symlink to the folder with the name "..data". This behavior cannot be prevented. It seems like there was a change between Liferay 7.1 and 7.2 in how the the configs folder is parsed for *.config files.

Reproduced on master on the 27th of May 2020 (9617f95b39dbb47f032785f08b71932038e1bb9e).