Issues

Select view

Select search mode

 

CLONE - scheduled task errors when shutting down tomcat

Description

when I shutdown the latest snapshot, I'm seeing all these errors, it's been happening with previous 5.3 snapshots too

just starting lucee, opening one page on the virtual host and then stopping the service triggers all these error messages

 

 

Environment

Apache Tomcat/8.5.31
JVM 1.8.0_181-b13
5.3.1.74-SNAPSHOT

relates to

Details

Assignee

Reporter

Priority

Labels

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

Affects versions

Created 8 April 2019 at 22:39
Updated 5 June 2020 at 15:03

Activity

Show:

Zac Spitzer31 January 2020 at 11:38

now seeing a roughly 1m delay on shutting down with 5.3.5.69-SNAPSHOT

Michael Offner17 June 2019 at 08:53

we further improved the implementation, but still work ti encapsulate the problem.

Brad Wood18 May 2019 at 01:53
Edited

I believe this ticket has had a negative effect on the FusionReactor line performance monitor, which is used by TestBox 3.0 for code coverage reporting. Specifically, this line which seems to kill the currently executing thread:

https://github.com/lucee/Lucee/commit/81f5520f20deeddbc25f811a571a60983c5cf684#diff-2bd4a0f2e5824a28a0ea12b1d5ff663dR41

When Fusionreactor enables the line performance monitor, it issues a reset() of the Lucee engine. I believe this is to clear out any cached class files so it can instrument them when they compile again. The problem is that Lucee kills the request dead when FR issues the reset() call, causing a 500 error to come back.

I will enter in a ticket for this.

Zac Spitzer13 May 2019 at 22:34

file a separate bug please (after checking against the latest stable release, 5.2.9.31 is old)

Vikrant13 May 2019 at 19:00

After deleting scheduled task it still runs. Currently I had to delete the whole web-inf folder. IIS recreates the folder and problem gone. Looks like caching issue. Please fix it. If I am not wrong this also causes to create duplicate task runs.

Flag notifications