Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052423POS2Corepublic2023-05-11 14:132023-05-11 14:13
Reportercaristu 
Assigned ToTriage Platform Base 
PriorityhighSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052423: Too verbose log when an error happens in a terminal property service
DescriptionThe error log printed when there is an error in service which calculates a terminal property is too verbose.
Steps To Reproduce1- Apply the attached patch in org.openbravo.retail.posterminal module to force an error during the calculation of the terminal properties
2- Do a fresh login in POS2. After the error is fired note that the error is printed in the log several times making the error too verbose
Proposed SolutionReview all the parts making the extra error printing in the log like this one: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/blob/master/src/org/openbravo/retail/posterminal/term/Terminal.java#L318 [^]
Additional Information
TagsNo tags attached.
Relationships
related to defect 0052418 closed Triage Platform Base Errors in terminal properties are not properly managed in the UI 
Attached Filesdiff forceError.diff (1,090) 2023-05-11 14:13
https://issues.openbravo.com/file_download.php?file_id=18522&type=bug
Issue History
Date ModifiedUsernameFieldChange
2023-05-11 14:13caristuNew Issue
2023-05-11 14:13caristuAssigned To => Triage Platform Base
2023-05-11 14:13caristuTriggers an Emergency Pack => No
2023-05-11 14:13caristuIssue generated from0052418
2023-05-11 14:13caristuRelationship addedrelated to 0052418
2023-05-11 14:13caristuFile Added: forceError.diff

There are no notes attached to this issue.