It is necessary to add more debug traces in the SessionErrors class

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.1.X, 7.2.X, 7.3.X, Master
• Fix Version/s: 7.0.X, 7.1.10 DXP FP26, 7.1.10.7 SP7, 7.1.X, 7.2.10 DXP FP15, 7.2.X, 7.3.10.3 DXP SP3, 7.3.X, 7.4.2 CE GA3, 7.4.13 DXP GA1, Master
• Component/s: Core Infrastructure
• Labels:
  • ee-ts
  • liferay-dxp-71-sp7
  • liferay-dxp-73-sp3
  • liferay-fix-pack-dxp-3-7310
  • liferay-fixpack-dxp-15-7210
  • liferay-fixpack-dxp-26-7110
  • liferay-fixpack-dxp-3-7310
• Branch Version/s:
  7.3.x, 7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/10164

We should add more debug traces in the SessionErrors class to be able to trace all the errors that are sent from the backend to the frontend.

Sometimes, the Liferay code handles an exception and stores it in the SessionErrors object but it doesn't write any trace. This makes harder to diagnose some customer problems as we will have to create a debug hotfix that it is time consuming.

Adding some debug traces in the SessionErrors class will allow us to detect the root cause of any error that is shown in the user interface even if the class that calls SessionErrors doesn't write any trace.

Steps to reproduce

1. Go to Control Panel => System => Server Administration => Log levels
2. Activate DEBUG trace for: com.liferay.portal.kernel.servlet.SessionErrors
3. Go to Control Panel => Configuration => Instance settings => Instance configuration
4. Edit the instance setting and configure an invalid mail domain, for example "##invalid##"
5. Save the changes => an error is displayed in the user interface
6. Check the log file:
   • Expected behavior: A debug trace related to the validation error is written to the log file with the related exception
   • Wrong behavior: No debug trace related to the validation error is written to the log file