Legacy Knowledge Base
Published Sep. 10, 2025

Why are entries in my Liferay DXP bundle (such as Organization Types) duplicating every restart

Written By

Nathan Roberts

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

  • In some situations there have been reports of OSGi entries within a Liferay DXP 7.1 bundle replicating every restart.
    • At first there is one entry for a given configuration, then following a restart there are two, following another there are three, etc.

Environment

  • Liferay DXP 7.1 with configured and deployed OSGi files
  • MacOS is the only environment this issue has been observed in

Resolution

  • Confirm that the liferay.home= property has been configured to an absolute file path or is using its default configuration: liferay.home=${resource.repositories.root}
    • When a relative file path is configured it is possible for the OSGi files to replicate due to the bundle reading the osgi files as belonging to a different file path than is recorded in the database. 

Additional Information

  • If an issue like this one persists despite the identified Resolution please open a ticket within the Liferay Help Center so that it can be investigated by our Support Team.
Did this article resolve your issue ?

Legacy Knowledge Base