Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0046596
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] Coremajoralways2021-05-10 07:432021-05-13 07:23
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0046596: no stack traces in terminal log

DescriptionWhen pos2 is deployed in production mode (from Tomcat), the messages generated in the terminal log do not include stack trace at all.
Steps To Reproduce1. Use the pos2 deployed in production mode (ie. livebuilds)
2. Check in the terminal log technical messages.
  ERROR: they finish with "stackTrace: undefined"
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0127930)
hgbot (developer)
2021-05-10 10:03

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/223 [^]
(0128053)
hgbot (developer)
2021-05-13 07:23

Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/223 [^]
(0128054)
hgbot (developer)
2021-05-13 07:23

Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core [^]
Changeset: 94a8ae05f2c1ecfcd65e4b81060c3a545904f552
Author: Asier Lostalé <asier.lostale@openbravo.com>
Date: 2021-05-13T05:22:58+00:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/94a8ae05f2c1ecfcd65e4b81060c3a545904f552 [^]

fixed BUG-46596: no stack traces in terminal log from core2

core2 applications when served in production mode, did not include any
stack trace in their terminal log. This occurred because ob-log's
getStackTrace function tried to remove unrelevant callers by removing
all the callers in the stack from OB.error/warn/info. To pick the 1st
relevant stack element function name was used to compare.

In core2 webpack mangles function names so this comparision didn't work
resulting on empty stack traces.

getStackTrace function is a private function which is always invoked
from the same place, we don't need to compare by function name but just
pick the stack from the known position, this works regardless function
name mangling.

---
M web/org.openbravo.mobile.core/source/utils/ob-log.js
---

- Issue History
Date Modified Username Field Change
2021-05-10 07:43 alostale New Issue
2021-05-10 07:43 alostale Assigned To => Retail
2021-05-10 07:43 alostale Resolution time => 1622412000
2021-05-10 07:43 alostale Triggers an Emergency Pack => No
2021-05-10 07:43 alostale Assigned To Retail => alostale
2021-05-10 07:43 alostale Status new => scheduled
2021-05-10 07:45 alostale Steps to Reproduce Updated View Revisions
2021-05-10 10:03 hgbot Note Added: 0127930
2021-05-13 07:23 hgbot Resolution open => fixed
2021-05-13 07:23 hgbot Status scheduled => closed
2021-05-13 07:23 hgbot Note Added: 0128053
2021-05-13 07:23 hgbot Fixed in Version => RR21Q3
2021-05-13 07:23 hgbot Note Added: 0128054


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker