thread debug logs total time is always zero

Description

The total time (i.e execution time) for the thread's in debugging log entry is always zero. The execution time for query inside the thread logs is as expected but still, the thread execution time shows zero.

 

The debug entry for the template and execution time is logged while on the requested page is included, So it just doesn't work for child threads

https://github.com/lucee/Lucee/blob/07ca0744b727165d02543639404d6bb60c95247f/core/src/main/java/lucee/runtime/PageContextImpl.java#L1022-L1047

 

Environment

None

Attachments

3
  • 29 Sept 2022, 09:59 am
  • 28 Sept 2022, 01:43 pm
  • 28 Sept 2022, 01:43 pm

Activity

Show:

Pothys - MitrahSoft 31 October 2022 at 10:37

I've checked this ticket with the fixed version 6.0.0.278-SNAPSHOT and now the thread debug logs execution time was set as expected.

Pothys - MitrahSoft 31 October 2022 at 06:19
Edited

Those thread-related tests failed due to that pc.getConfig in Single context mode is not a type of configImpl

 

https://github.com/lucee/Lucee/blob/df3de861d84b1c56a7361d1036e4d486f01fd21a/core/src/main/java/lucee/runtime/thread/ChildThreadImpl.java#L187

Exception in thread "cfthread-1" java.lang.ClassCastException: lucee.runtime.config.SingleContextConfigWeb cannot be cast to lucee.runtime.config.ConfigImpl at lucee.runtime.thread.ChildThreadImpl.execute(ChildThreadImpl.java:187) at lucee.runtime.thread.ChildThreadImpl.run(ChildThreadImpl.java:151)

Zac Spitzer 28 October 2022 at 16:30

Zac Spitzer 28 October 2022 at 15:26

this PR broke the build disappointed face

Fixed

Details

Assignee

Reporter

Priority

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Created 28 September 2022 at 13:43
Updated 31 October 2022 at 10:37
Resolved 31 October 2022 at 10:37

Flag notifications