Legacy Knowledge Base
Published Jul. 2, 2025

Disabled commerce shows error about missing bundles at startup

Written By

Solyom Nagy-Györkös

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Commerce is disabled by using the enterprise.product.commerce.enabled=false property

  • Starting up with this property the following error is logged at startup:

    WARN  [main][SystemCheckOSGiCommands:137] Declarative Service Unsatisfied Component Checker check result:
    _Bundle {id: 1027, name: com.liferay.site.initializer.extender, version: 1.0.44}
    _       Declarative Service {id: 2908, name: com.liferay.site.initializer.extender.internal.CommerceSiteInitializer, unsatisfied references:
    _            {name: _catalogResourceFactory, target: null}
    _            {name: _channelResourceFactory, target: null}
    _            {name: _commerceAccountRoleHelper, target: null}
    _            {name: _commerceCatalogLocalService, target: null}
    _            {name: _commerceChannelLocalService, target: null}
    _            {name: _commerceChannelService, target: null}
    _            {name: _commerceCurrencyLocalService, target: null}
    _            {name: _commerceInventoryWarehousesImporter, target: null}
    _            {name: _commerceNotificationTemplateLocalService, target: null}
    _            {name: _cpDefinitionLocalService, target: null}
    _            {name: _cpDefinitionsImporter, target: null}
    _            {name: _cpInstanceLocalService, target: null}
    _            {name: _cpMeasurementUnitLocalService, target: null}
    _            {name: _cpOptionsImporter, target: null}
    _            {name: _cpSpecificationOptionsImporter, target: null}
    _            {name: _optionResourceFactory, target: null}
    _            {name: _portletSettingsImporter, target: null}
    _            {name: _productOptionResourceFactory, target: null}
    _            {name: _productSpecificationResourceFactory, target: null}_ } [Sanitized]
  • Alternatively: At startup, this WARN message might not visible in the log. Only if the command ds:unsatisfied is run in the Gogo shell.
  • Using Gogo shell, 2 packages for Commerce are active after startup:

    g! lb commerce
    START LEVEL 20
    ID|State |Level|Name
    228|Active | 10|Liferay Commerce - Liferay Commerce - Impl (1.0.0)|1.0.0
    1135|Active | 10|Liferay Commerce - Liferay Commerce - API (1.0.0)|1.0.0

Environment

  • Liferay DXP 7.4 below U48
  • Commerce 4.0

Resolution

  • This message log is only a warn, which means the use of the portal is safe, and it should work as intended.
  • However, if you want to hide it from your log, then navigate to Control Panel > (Configuration) System Settings > (Platform) Module Container > Component Blacklist tab, and blacklist the below component: com.liferay.site.initializer.extender.internal.CommerceSiteInitializer

Additional Information

  • That unsatisfied warn is expected since Commerce is still disabled.  Essentially, they moved Commerce Specific code over to CommerceSiteInitializer so the OSGI component check would only fail in that area of the code.
  • Please note that the property and the possibility of disabling Commerce in Liferay have been removed in DXP 7.4-Update 48 and above
Did this article resolve your issue ?

Legacy Knowledge Base