Open maxhbr opened 5 years ago
This does most likely not affect us because we are storing no content inside Liferay. Even the search field on the top right calls our search page.
Theoretically it can be disabled by creating the file ${LIFERAY_INSTALL}/osgi/configs/com.liferay.portal.bundle.blacklist.internal.BundleBlacklistConfiguration.config
with the following content:
blacklistBundleSymbolicNames="com.liferay.portal.search.elasticsearch6.impl"
However I'm not sure about side effect when disabling it. I would not take that chance.
Another approach might be to change the log level of com.liferay.portal.search.elasticsearch6.internal.connection.EmbeddedElasticsearchConnection
to ERROR
. For some reason disabling did not work and Liferay is resetting the log level to WARN
again.
In general, disabling this warning is a matter of deployment and cannot be configured via sw360 itself.
@mcjaeger @maxhbr Therefore I think it can be closed here.
Hm, it should be in the wiki or somehow documented that liferay is being used with the default setup since we re not using anything else from liferay.
The Liferay warns on startup, that it uses an embedded Elasticsearch, which should not be used in production. Does that affect us? Can we hide this warning?