Changing log level for allowed inconsistences in web content referencing unexistent documents

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.1.10 DXP FP9, 7.1.10.2 SP2, 7.1.3 CE GA4, 7.1.X, Master
• Component/s: WCM > Upgrade
• Labels:
  • ee-ts
  • liferay-dxp-71-sp2
  • liferay-fixpack-dxp-9-7110
• Branch Version/s:
  7.1.x
• Backported to Branch:
  Committed
• Story Points: 2
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/69016

Precondition:

1. Running upgrade from 7.0 to 7.1
2. Existing web contents with references to documents (of image type) and those documents were deleted.

Observed behaviour:
Following exception trace is showed in the log:

2019-01-31 15:29:02.586 ERROR [main][UpgradeContentImages:222] Unable to get file entry with group ID 32404, folder ID 287851, and file name 178075
com.liferay.document.library.kernel.exception.NoSuchFileEntryException: No DLFileEntry exists with the key {groupId=32404, folderId=287851, title=178075}
	at com.liferay.portlet.documentlibrary.service.impl.DLFileEntryLocalServiceImpl.getFileEntry(DLFileEntryLocalServiceImpl.java:1342)
	at sun.reflect.GeneratedMethodAccessor450.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:153)
	at com.liferay.portal.spring.transaction.DefaultTransactionExecutor._execute(DefaultTransactionExecutor.java:203)
	at com.liferay.portal.spring.transaction.DefaultTransactionExecutor.execute(DefaultTransactionExecutor.java:94)
	at com.liferay.portal.spring.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:113)
	at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:130)
	at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:55)
	at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:130)
	at com.liferay.portal.spring.aop.ChainableMethodAdvice.invoke(ChainableMethodAdvice.java:55)
	at com.liferay.portal.spring.aop.ServiceBeanMethodInvocation.proceed(ServiceBeanMethodInvocation.java:130)
	at com.liferay.portal.spring.aop.ServiceBeanAopProxy.invoke(ServiceBeanAopProxy.java:125)
	at com.sun.proxy.$Proxy120.getFileEntry(Unknown Source)
	at com.liferay.portal.repository.liferayrepository.LiferayLocalRepository.getFileEntry(LiferayLocalRepository.java:360)
	at com.liferay.portal.repository.util.LocalRepositoryWrapper.getFileEntry(LocalRepositoryWrapper.java:221)
	at com.liferay.portal.repository.util.LocalRepositoryWrapper.getFileEntry(LocalRepositoryWrapper.java:221)
	at com.liferay.portal.repository.util.LocalRepositoryWrapper.getFileEntry(LocalRepositoryWrapper.java:221)
	at com.liferay.portal.repository.capabilities.CapabilityLocalRepository.getFileEntry(CapabilityLocalRepository.java:313)
	at com.liferay.portal.portletfilerepository.PortletFileRepositoryImpl.getPortletFileEntry(PortletFileRepositoryImpl.java:547)
	at com.liferay.portal.kernel.portletfilerepository.PortletFileRepositoryUtil.getPortletFileEntry(PortletFileRepositoryUtil.java:266)
	at com.liferay.journal.internal.upgrade.v1_1_5.UpgradeContentImages._getFileEntryById(UpgradeContentImages.java:218)
	at com.liferay.journal.internal.upgrade.v1_1_5.UpgradeContentImages.convertTypeImageElements(UpgradeContentImages.java:90)
	at com.liferay.journal.internal.upgrade.v1_1_5.UpgradeContentImages.updateContentImages(UpgradeContentImages.java:176)
	at com.liferay.journal.internal.upgrade.v1_1_5.UpgradeContentImages.doUpgrade(UpgradeContentImages.java:135)
	at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:96)
	at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:138)
	at com.liferay.portal.upgrade.internal.executor.UpgradeExecutor$UpgradeInfosRunnable.run(UpgradeExecutor.java:159)
	...
	...
	...
	...
	...
	...

Expected behaviour:

• Using WARN level instead of ERROR for the exception because that inconsistency is allowed by product.
• Only print data related to data inconsistency.
• And printing the complete exception in DEBUG level for information proposes.