Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0033124 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Retail Modules] Web POS | minor | have not tried | 2016-06-02 18:35 | 2016-06-03 00:03 | |||||||
| Reporter | shuehner | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0033124: OrderLoader timing debug reports 'executeHooks' inside 'processPayment' timing | |||||||||||
| Description | OrderLoader 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 Reproduce | read code around this line in Orderloader // Call all OrderProcess injected. And check where the time taken for it is reported. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0086967) shuehner (administrator) 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 |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2016-06-02 18:35 | shuehner | New Issue | |
| 2016-06-02 18:35 | shuehner | Assigned To | => Retail |
| 2016-06-02 18:35 | shuehner | Triggers an Emergency Pack | => No |
| 2016-06-03 00:03 | shuehner | Note Added: 0086967 | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |