How to resolve a "Failed to define class from Service Module Loader" error
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
- Upon installation of security-hotfix-lsv-45 in Liferay Portal bundled with JBoss, a "Failed to define class" error is generated in the Liferay logs.
Resolution
-
This issue stems from the fact JBoss does not know where to find SecureXMLFactoryProviderUtil.class and SecureXMLFactoryProvider.class, due to an existing index. These two files are required when instantiating SecureXMLFactoryProviderImpl from the portal-impl.jar.
- To remedy this error:
-
- Shut down your Liferay Portal.
- Delete the portal-service.jar.index found here: <LIFERAY_HOME>/<Jboss>/modules/com/liferay/portal/main/portal-service.jar.index
- Restart your Liferay Portal.
Did this article resolve your issue ?
