Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
7.0.0 Alpha 3
-
None
-
9
-
4
-
Regression Bug
Description
After LPS-51908 changes, log traces of Staging and LAR import/export does not display the information of exported objects:
Steps to reproduce
- Add log traces of com.liferay.export.import at DEBUG level
- Create 4 webcontents
- Do any Staging or LAR export/import operation
- Expected behavior:
Log traces display groupId, className and primaryKey of objects that are exported/imported (same behavior than 6.2 version):
01:16:09,492 INFO [liferay/background_task-1][PortletDataContextListenerImpl:35] Export /group/11637/com.liferay.portlet.journal.model.JournalArticle/36957.xml 01:16:09,596 INFO [liferay/background_task-1][PortletDataContextListenerImpl:35] Export /group/11637/com.liferay.portlet.journal.model.JournalArticle/37433.xml 01:16:09,663 INFO [liferay/background_task-1][PortletDataContextListenerImpl:35] Export /group/11637/com.liferay.portlet.journal.model.JournalArticle/37424.xml 01:16:09,745 INFO [liferay/background_task-1][PortletDataContextListenerImpl:35] Export /group/11637/com.liferay.portlet.journal.model.JournalArticle/92100.xml .... 01:17:17,441 INFO [WebContainer : 3][PortletDataContextListenerImpl:42] Import /group/11637/com.liferay.portlet.journal.model.JournalArticle/462949-expando.xml 01:17:19,001 INFO [WebContainer : 3][PortletDataContextListenerImpl:42] Import /group/11637/com.liferay.portlet.journal.model.JournalArticle/530580.xml 01:17:19,218 INFO [WebContainer : 3][PortletDataContextListenerImpl:42] Import /group/11637/com.liferay.portlet.journal.model.JournalArticle/530580.xml 01:17:19,560 INFO [WebContainer : 3][PortletDataContextListenerImpl:42] Import /group/11637/com.liferay.portlet.journal.model.JournalArticle/530580-expando.xml 01:17:20,180 INFO [WebContainer : 3][PortletDataContextListenerImpl:42] Import /group/11637/com.liferay.portlet.journal.model.JournalArticle/439934.xml
- Wrong behavior:
Log traces does not display groupId nor primary key of objects that are exported/imported :
18:49:18,097 DEBUG [liferay/background_task-2][LoggerExportImportLifecycleListener:389] Staged model com.liferay.journal.model.JournalArticle export started 18:49:18,110 DEBUG [liferay/background_task-2][LoggerExportImportLifecycleListener:403] Staged model com.liferay.journal.model.JournalArticle export succeeded 18:49:18,113 DEBUG [liferay/background_task-2][LoggerExportImportLifecycleListener:389] Staged model com.liferay.journal.model.JournalArticle export started 18:49:18,122 DEBUG [liferay/background_task-2][LoggerExportImportLifecycleListener:403] Staged model com.liferay.journal.model.JournalArticle export succeeded ... 18:49:12,989 DEBUG [liferay/background_task-1][LoggerExportImportLifecycleListener:433] Staged model com.liferay.journal.model.JournalArticle import started 18:49:13,134 DEBUG [liferay/background_task-1][LoggerExportImportLifecycleListener:447] Staged model com.liferay.journal.model.JournalArticle import succeeded 18:49:13,139 DEBUG [liferay/background_task-1][LoggerExportImportLifecycleListener:433] Staged model com.liferay.journal.model.JournalArticle import started 18:49:13,292 DEBUG [liferay/background_task-1][LoggerExportImportLifecycleListener:447] Staged model com.liferay.journal.model.JournalArticle import succeeded
- Expected behavior:
This issue is very problematic, as without that primaryKey information at support we cannot diagnose customers issues at Staging or LAR export/import in case of failure