Two instance of CLI cause class loading issues from OSGI bundles
Description
Lucee removed a Felix system property CommandBox has used to control how Felix works.
The name of the system property has now changed which explains why starting a second box instance would get Felix errors in the log. The
setting instructs Felix to NOT blow away the OSGI bundle cache when it starts up. Since the name of the setting was changed inside Lucee, Felix had gone back to its default behavior or deleting the OSGI bundle cache from disk which would bork already-running box instances.
As part of this fix, I’m going to remove the fix implemented in COMMANDBOX_1541 to hide Felix error logging by default. It turns out those messages were indicative of an issue, we just didn’t understand what it was.
This fix can be manually applied to any CommandBox 5.7.0 install right now by setting the java system property
Lucee removed a Felix system property CommandBox has used to control how Felix works.
The name of the system property has now changed which explains why starting a second box instance would get Felix errors in the log. The
setting instructs Felix to NOT blow away the OSGI bundle cache when it starts up. Since the name of the setting was changed inside Lucee, Felix had gone back to its default behavior or deleting the OSGI bundle cache from disk which would bork already-running box instances.
As part of this fix, I’m going to remove the fix implemented in COMMANDBOX_1541 to hide Felix error logging by default. It turns out those messages were indicative of an issue, we just didn’t understand what it was.
This fix can be manually applied to any CommandBox 5.7.0 install right now by setting the java system property
in the CLI.
https://commandbox.ortusbooks.com/usage/execution#ad-hoc-jvm-args-for-the-cli