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

ご覧のページは、お客様の利便性のために一部機械翻訳されています。また、ドキュメントは頻繁に更新が加えられており、翻訳は未完成の部分が含まれることをご了承ください。最新情報は都度公開されておりますため、必ず英語版をご参照ください。翻訳に問題がある場合は、こちらまでご連絡ください。

問題

• 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).

• This error persists with the correct portal property configurations outlined here: security-hotfix-lsv-45

環境

• Portal 6.1
• ポータル 6.2

解決

• 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. 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. 

追加情報

• Installing Fix Packs and Hotfixes on Liferay Portal 6.x EE
• LSV-45: Missing protection against common XML parsing attacks