How can I change Confluence XHTML content timout of 120 seconds?

[Eddie Connatser]

Any help will be greatly appreciated so thank you in advance!!! I am executing a large query on a Confluence page that takes several minutes to run (depending on your datasource "maxWait" setting as well as your "hibernate.c3p0.timeout"" property in your confluence.cfg.xml file). However, I get the same error message printed to the screen regardless of these settings. The error message printed to the screen says, "Rendering this content exceeded the timeout of 120 seconds". In the Confluence log it says: "com.atlassian.confluence.content.render.xhtml.XhtmlTimeoutException: Rendering this content exceeded the timeout of 120 seconds." Is there any way to adjust this Xhtml timeout setting in Confluence?

Note: A large query would be around 10-20k rows.

Kind regards,
Eddie

[Anatoli · Accepted solution]

Yes, a system administrator can change the timeout value through http://screencast.com/t/UJN78fBh8loy admin console -> security configuration.

Note that we don't recoment changing those values as 2 min should be more than enough to render any page. If a macro requires more than 2 mins you should be looking into how to improve the performance of that macro.

[Bob Swift]

Anyone using Confluence for SQL reporting, scripting, reporting macro, metadata or similar may need to raise the limit. Following the techniques in Page display performance tips and techniques especially Cache Plugin for Confluence and Automated caching . Too low a limit and these techniques will fail. Normal users see the pages almost immediately, but the automation needs a long enough render time to handle the complex queries and other techniques used. It needs to be as large as longest page render takes plus some buffer. In our case, likely 5 minutes would be reasonable to cover our most difficult pages with some room to cover performance slowdowns.

[Bob Swift]

Related to my comment above, there is now a better option using the Future macro (perferably used in combination with the Cache Macro). Not only does it provide better usability by allowing other content to be displayed and interacted with immediately, but there is a parameter that allows you to increase the render timeout for just an individual situation. This is preferable to making a global increase.

[Ethan Foulkes]

Bob Swift wins again! I've been using future macro since you added it in but just realized this option bypasses the Atlassian timeout limit. This is a huge help for some of our big report pages. Thanks Bob!

[Bob Swift]

Thanks. I would think with that praise the answer would at least warrent a +1 :)

[Deleted user]

I'll definitely test it too as soon as I can. Thanks Bob. You've got my +1 !

[Antony Galdi]

Seeing this timeout for pages with any more than a handful of JIRA macros added to it. Both systems run on the same server. Any tips for otimizing JIRA macro performance? Many confluence pages are failing to render because of this.

[Anatoli]

Hi Antony, in the latest version of JIRA macros we fixed the performance by batching multiple requests to the same server. You can download the new version from here or install it directly from confluence via add-on managment screen.

[Tom Moors]

The same problem here, CustomWare Reporting Plugin needs this amount of time for some content checking reports like eg validation of Scaffolded content.

[Bob Swift]

Please poke Atlassian on this. There are many cases for long running renders and it doesn't mean users have to wait at all using the Confluence Cache Plugin and suitable automation for rendering the page before the cache expires.

This is a serious incompatibility with 3.x. We could not upgrade without a good answer to this.

Here is a simple test:

{groovy} sleep(300000) {groovy}

[Stéphane Genin]

Hi,

I have the same problem with a JIRA Issues macro that retrieves lots of issues.

Is there a way to increase the timeout?

We have some performance issues on the JIRA side that we are currently fixing but in the meantime I don't want confluence customers to be impacted.

Stéphane

[David at David Simpson Apps]

120 seconds+? Your users must be very patient :) Could you optimise the query better? Have better indexing on the database side? Could you trigger a Confluence job that runs and caches the query in the background for faster delivery of the content.

[Eddie Connatser]

David,

Thank you for your response - I'm working with our database administrator to find out if our query can be optimized for efficiency.

Kind regards,
Eddie