Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Select search mode

 
1 of 1

Threading issue: the thread scope cannot be modified from outside the owner thread

Fixed

Description

I have no problem with this code:

But if I move the first line in the thread

I receive this error:

"ERROR","cfthread-0","06/22/2017","09:06:59","","cfthread-0;the thread scope cannot be modified from outside the owner thread;lucee.runtime.exp.ApplicationException: the thread scope cannot be modified from outside the owner thread
at lucee.runtime.thread.ThreadsImpl.errorOutside(ThreadsImpl.java:403)
at lucee.runtime.thread.ThreadsImpl.set(ThreadsImpl.java:274)
at lucee.runtime.type.util.StructSupport.set(StructSupport.java:249)
at lucee.runtime.util.VariableUtilImpl.set(VariableUtilImpl.java:407)
at lucee.runtime.PageContextImpl.set(PageContextImpl.java:1414)
at core.search.searchgateway_cfc$cf.threadCall(/contenscms/core/search/searchgateway.cfc:99)

My workaround was to move stResult as key of searchArgs.

Maybe the issue was introduced with this changeset?
https://github.com/lucee/Lucee/commit/f22a0573df89fe08ac0c97f869fc2aadcfac20a6

Environment

All

Details

Assignee

Reporter

Priority

Labels

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

Affects versions

Created 22 June 2017 at 10:36
Updated 10 March 2025 at 12:40
Resolved 9 February 2018 at 16:13

Activity

Show:

Adam Cameron10 March 2025 at 12:40

Sorry mate. Lucee’s in maintenance mode from our perspective now, and we don’t touch it unless we need to; other than to retire code form it, as we port chunks of functionality away. I only came back to this as the error was causing us some grief last week. But it’s transient enough we can just nod and go “yep, we know about that…”.

Zac Spitzer10 March 2025 at 12:35

can you ping me on any other tickets related to your show stopping backwards compat problems?

Adam Cameron10 March 2025 at 12:30

Ah yeah, nw then. I did not see the linked ticket, or indeed any mention of “we’ll follow this up on ”, which might have been a good signpost in these situations.

No idea about 6.2. We can move from 5.4.something due to show-stopping backwards compat breaks introduced in 5.4.something+0.1, let alone trying 6.x.

NB: I don’t expect a back ported fix or anything. Was more after some sort of acknowledgement of my previous comment (that the fix this ticket claims it made wasn’t actually a fix), but that was probs covered by linking to LDEV-3116.

From my perspective everything is A-OK with the current state on the other ticket,

Cheers for the follow-up.

Zac Spitzer8 March 2025 at 13:53

We have a linked ticket, but we'll open a new one as this re rather long, just confirming it's still not working in 6.2 yeah?

Adam Cameron8 March 2025 at 12:52

I wonder if anyone clocked in my previous comment “this is not fixed”? That something has been deployed is lovely, but… issue is still there, so it’s not resolved. Am not expecting miracles, but equally probs the ticket ought to be reopened.

Flag notifications