-
Suggestion
-
Resolution: Unresolved
-
None
-
48
-
109
-
NOTE: This suggestion is for Confluence Data Center. Using Confluence Cloud? See the corresponding suggestion.
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this ticket and weighing it up against our other opportunities, we have decided to transition it to 'Gathering interest' as we don't have plans to work on this in the near term.
Please continue to vote and watch this suggestion if it is important to your team, as we regularly review highly ranked tickets as potential roadmap items.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
Would like the ability to set the timeout threshold for a PDF Export. The following appears in the logs as a WARN
WARN [Long running task: PDF Space Export] [confluence.util.profiling.DefaultActivityMonitor] close Exceeded the threshold of 60000 ms: ActivitySnapshot{startTime=1425991343730, threadId=15781, threadName='Long running task: PDF Space Export', userId='', type='long-running-task', summary='PDF Space Export'}
When the threshold is reached, the link to the PDF is not displayed. Instead, an error message regarding the threshold is displayed. This leads a user to believe the file is not created since a link is not displayed and only this error is shown. Looking in the <Confluence Home>/temp, the file is there. If the timeout was configurable in UI, we would not see confusion between this error appearing and the file actually being generated.
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Failed to load
-
Page Failed to load
-
-
-
-
-
-
-
-
-
-
[CONFSERVER-36883] Ability to change the timeout threshold in the Confluence UI
@Jonathan,
thank you very much for your quick reply.
Unfortunately we don't have the same problem, even with advanced logging I don't get such error. I found some permission errors, which I'm analyzing now. If we solve the problem, I will be happy to provide our solution.
Thanks a lot and best regards
@Tom
It wasn't an easy one, hope this will help you. Do a search in your logs for this exception;
org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.atlassian.confluence.spaces.SpaceDescription#1070902655]
This was a corrupted space, which had to be deleted from the BD itself, we then followed this procedure to delete space 1070902655;
Hi @Jonathan,
we have the same problem with the plugin. Can you tell me what you mean by corrupted space? What exactly has been wrong with the space and how do I find out?
Thanks a lot and best regards, Tom
@Aron Gombas
Finally just found the problem was not related to this, but a corrupted space after trying an import. Had to delete the space from the database, but better content archiving is now working properly, sorry if I created any confusion, not related after all !
@Jonathan Are you sure you "cannot use" the Archiving app?
(I'd tend to think that for that app, it is really a warning that is written to the log, but otherwise the long running task is not stopped. Some it is annoying, but the functionality is there.)
We cannot use better content archiving because of this timeout (we have a lot of spaces);
2020-12-21 16:01:23,965 WARN [Long running task: Content Event Indexing [CARCH]] [confluence.util.profiling.DefaultActivityMonitor] close Exceeded the threshold of 60000 ms: ActivitySnapshot{startTime=1608584150351
So even now there is no way to change the threshold timeout settings???
Ran into this today ... Confluence 7.4.1 while trying to delete a space that has one page in it.
Attempted to use ScriptRunner and the same exception was thrown.
I'm experiencing this issue when applying a page level restriction. The UI throws an error - but the operation appears to be completed. successfully.
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this ticket and weighing it up against our other opportunities, we have decided to transition it to 'Gathering interest' as we don't have plans to work on this in the near term.
Please continue to vote and watch this suggestion if it is important to your team, as we regularly review highly ranked tickets as potential roadmap items.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center