Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
Problem Definition
An User Macro is a great way to extend Confluence functionalities, since the administrator can code virtually anything.
Depending on what the macro is coded for, its operation may take a long time to complete and, while it is running, it is prone to impact on Confluence performance.
Currently, there's no mechanism to kill the inner operation performed by the user macro if it is running for longer than a threshold.
Suggested Solution
Introduce a configurable timeout to user macros and an option to asynchronously run them.
If a macro is taking a long time to complete, kill the macro rendering thread after the specified threshold.
Although the macro should be extensively tested for performance and security reasons, it would be great if Confluence could safeguard itself from expensive operations.
Workaround
_No workaround so far.