ISSUE-47974: Fix bad logging use log4j instead of printStackTrace (!1) · Merge requests · openbravo / product / Unsupported / modules / org.openbravo.module.validto · GitLab

As of 2024-05-14 a change has been implemented to enforce access token expiry. If you see higher numbers of HTTP 401 responses, please check tokens that may have expired. For more details, including how to mitigate disruption, please check our docs guide on Expired Access Tokens. If you have a support contract, you may open a support ticket for additional assistance.

The source project of this merge request has been removed.

Stefan Huehner requested to merge (removed):fix/47974 into master Jul 26, 2022

ValidToProcess let log4j.error report the stacktrace not need to do that manually and worse. Also change .debug into .error which looks more adequate for date format parsing error
ValidToUtility two cases of same letting log4j.error log the stacktrace as above. In one also upgrade .debug to .error for consistency