Mayura Wijeyaratne created OLINGO-1320:
------------------------------------------
Summary: Debug Response is not created due to JVM Optimization
Key: OLINGO-1320
URL: https://issues.apache.org/jira/browse/OLINGO-1320
Project: Olingo
Issue Type: Bug
Components: odata2-core
Affects Versions: (Java) V4 4.4.0
Reporter: Mayura Wijeyaratne
Attachments: JVMOptimization.diff
There is a performance optimization in JVM when an exception is thrown a few
times in a certain period of time, it doesn't send the stack trace of the
exception any more.
"The compiler in the server VM now provides correct stack backtraces for all
"cold" built-in exceptions. For performance purposes, when such an exception is
thrown a few times, the method may be recompiled. After recompilation, the
compiler may choose a faster tactic using preallocated exceptions that do not
provide a stack trace. "
Olingo always expects the stack trace to be there in DebugTabStacktrace.java
file, and when there is no stack trace it throws a generic error "ODataLibrary:
Could not assemble debug response." and all the other information gets lost.
In the patch I have attached to this task, I have done a check to see if there
is a stack trace and if there is not, given a suggestion as to why, keeping the
other information intact.
Do consider that, there can be instances without any stack trace, in your
future releases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
