Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

PortalContextLoaderListener with Runtime Exception

Written By

Thanga Meena

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

  • After upgrading the Liferay portal DB from 6.2 to 7.2 successfully, Unable to start the server.
  • Below error occurs: [# Error1] 
27-Dec-2019 21:01:10.432 SEVERE [main] org.apache.catalina.core.StandardContext.listenerStart Exception sending context initialized event to listener instance of class [com.liferay.portal.spring.context.PortalContextLoaderListener]
      java.lang.RuntimeException: org.osgi.framework.BundleException: Exception in com.liferay.portal.configuration.persistence.internal.activator.ConfigurationPersistenceImplBundleActivator.start() of bundle com.liferay.portal.configuration.persistence.impl.

Environment

  • Upgrade environment:
    • Liferay DXP 6.2 - Souce version of the portal 
    • Liferay DXP 7.2 - Destination version of the portal
    • DB upgrade client version: com.liferay.portal.tools.db.upgrade.client-3.0.1

Resolution

  • Follow the workaround as suggested in LPS-86404
    • Execute the below query [Workaround - Oracle]
UPDATE CONFIGURATION_ SET DICTIONARY = ' ' WHERE CONFIGURATIONID = 'org_apache_felix_cm_impl_DynamicBindings' AND DICTIONARY IS NULL
  • After following the above workaround, the server gets started successfully.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?