-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.0 DXP GA1, 7.0.X, Master
-
Fix Version/s: 7.0.0 DXP FP40, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, 7.1.0 M1, 7.1.X, Master
-
Component/s: Core Infrastructure > DB Upgrade Client
-
Branch Version/s:7.0.x
-
Backported to Branch:Committed
-
Story Points:1
-
Fix Priority:3
-
Git Pull Request:
DB Upgrade Client: in case of exception, upgrade commands of gogo console:
- upgrade:execute
- upgrade:executeAll
doesn't display stacktrace
For more information about upgrade process, see: https://dev.liferay.com/discover/deployment/-/knowledge_base/7-0/running-the-upgrade-process
Steps to reproduce
- Install Liferay 6.2
- Create a webcontent using basic structure
- Stop Liferay 6.2
- In order to cause an error during upgrade, execute following sql update in 6.2 database (in this case we can use an direct SQL because we just want to demonstrate that our way to print log does not work prperly):
update JournalArticle set content=''
- Install Liferay 7.0
- Create a file called com.liferay.portal.upgrade.internal.configuration.ReleaseManagerConfiguration.cfg in LIFERAY_HOME/osgi/configs/
- Add autoUpgrade=false inside of previous created file
- Go to LIFERAY_HOME/tools/portal-tools-db-upgrade-client
- Execute upgrade: java -jar com.liferay.portal.tools.db.upgrade.client.jar
- Wait until core upgrade is executed and gogo shell is open
- Execute upgrade:executeAll
- After all commands are executed, execute again: upgrade:execute com.liferay.journal.service
- Expected behavior: Full stacktrace is printed
- Wrong behavior: Only first line of exception is printed
gogo: RuntimeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.xml.DocumentException: Error on line -1 of document : Premature end of file. Nested exception: Premature end of file.
- Expected behavior: Full stacktrace is printed
- relates
-
LPS-92326 Missing information in upgrade's log when running Gogo commands
- Closed