Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0033124Retail ModulesWeb POSpublic2016-06-02 18:352016-06-03 00:03
Reportershuehner 
Assigned ToRetail 
PrioritynormalSeverityminorReproducibilityhave 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
Summary0033124: OrderLoader timing debug reports 'executeHooks' inside 'processPayment' timing
DescriptionOrderLoader has debug code to track time taken for each 'group of actions'.

however executeHooks (custom code from modules) is reported inside 'process payments' debug.

Which does not make sense and probably adding when hooks it was forgotten to add new debug section.
Steps To Reproduceread code around this line in Orderloader
// Call all OrderProcess injected.

And check where the time taken for it is reported.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-06-02 18:35shuehnerNew Issue
2016-06-02 18:35shuehnerAssigned To => Retail
2016-06-02 18:35shuehnerTriggers an Emergency Pack => No
2016-06-03 00:03shuehnerNote Added: 0086967

Notes
(0086967)
shuehner   
2016-06-03 00:03   
After reporting the bug some more checking reveals that quite some more parts are broken with respect to debug logging.

There is code roughly 5ms running even before t0 timestamp
and
+ t4..t5
+ t5..t6 are not covered in the main/final log4j. timing statement

So probably all the debug/timing logging should be reviewed once