legacy-knowledge-base
Publicado Jul. 25, 2002

How to resolve a "Failed to define class from Service Module Loader" error

written-by

Caleb Bartles

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

learn-legacy-article-disclaimer-text

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.
    • Failed to define class com.liferay.portal.security.xml.SecureXMLFactoryProviderImpl in Module "deployment.ROOT.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link com/liferay/portal/security/xml/SecureXMLFactoryProviderImpl (Module "deployment.ROOT.war:main" from Service Module Loader).

Environment

  • Portal 6.1
  • Portal 6.2

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:
      1. Shut down your Liferay Portal. 
      2. Delete the portal-service.jar.index found here: <LIFERAY_HOME>/<Jboss>/modules/com/liferay/portal/main/portal-service.jar.index
      3. Restart your Liferay Portal. 

Additional Information

did-this-article-resolve-your-issue

legacy-knowledge-base