Ticket #138 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Parse File Lock Timeout

Reported by: dickbob Owned by: scorfield
Type: defect Priority: normal
Milestone: Fusebox 5.1 Component: Miscellaneous
Version: 5.0 Severity: normal
Keywords: Cc:

Description

Conditions:

Development-circuit-load mode
Long running page
Two or more browsers/users hitting to the same circuit.fuseaction at the same time

Result:
Error "A timeout occurred while attempting to lock /mydomain.com/parsed/mycircuit.myfuseaction.cfm"

Attachments

Change History

Changed 2 years ago by scorfield

  • owner changed from sean@corfield.org to scorfield
  • status changed from new to assigned
  • milestone changed from General Release to Fusebox 5.1

This occurs because development-circuit-load mode uses exclusive locks on executing the parsed file and then the exclusive lock on creating the parsed file times out because it is only 30 (whereas the others are 300).

Likely fix: add a timeout parameter to fusebox.xml that is used on all locks. Make it default to 300.

Changed 2 years ago by scorfield

  • status changed from assigned to closed
  • resolution set to fixed

(In [279]) Fixes #138 by extending timeout on creating parsed file from 30 to 300
(so it won't time out waiting for an exclusive lock on compiling a request).
At least, I *think* this is the fix for the symptoms reported.

Note: See TracTickets for help on using tickets.