We have the same issue if the user view a page with a lof of included pages and attachments. Is there any solutions for this issue ?? Why is it resolved?

Hi Jan, unless you can reproduce it reliably, it's probably best to raise a support ticket at https://support.atlassian.com and attach the image to the case. That way we can work out if it's something specific to your environment, the image, or something else.

Hi Robert,

we are still seeing this error. In our case a 4 core Windows 2008 R2 with 12GB RAM and 10GBit SAN in background. Error happens with a 50kb 460*580 PNG.

Error:

2015-04-07 08:28:01,389 WARN [ajp-bio-192.168.2.188-8009-exec-59] [confluence.image.effects.ImageFilterServlet] transformAndRespond Timed out while doing the transform
– referer: https://connect.schb.local/confluence/pages/releaseview.action?pageId=46498819 | url: /confluence/download/attachments/46498819/image-001.png | userName: abc
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at com.atlassian.confluence.image.effects.ImageFilterServlet.transformAndRespond(ImageFilterServlet.java:295)
at com.atlassian.confluence.image.effects.ImageFilterServlet.writeTransformToResponse(ImageFilterServlet.java:195)
at com.atlassian.confluence.image.effects.ImageFilterServlet.doGetInTransaction(ImageFilterServlet.java:155)
at com.atlassian.confluence.image.effects.ImageFilterServlet.access$000(ImageFilterServlet.java:62)
at com.atlassian.confluence.image.effects.ImageFilterServlet$1.doInTransaction(ImageFilterServlet.java:124)
at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)

As this happens on a server with virtually NO LOAD and enough memory. When testing I was the ONLY user on the server, so please reopen this issue and investigate..

How can I attach the image causing the problem?

This is happening to me on a 24 core machine with a load less than 1, on fusion IO disks, and memory usage is 28337/96704M...
The image we used was a 90kb PNG. 902 × 594

Timeout elsewhere?

Yes, that's correct. Once the image effect has been applied, the result is cached on disk and reused from then on. So this should only be a temporary situation.

If the images themselves are too big/complex for Confluence to handle, you might need to shrink them before putting them into Confluence.

I'll close this issue as "Not a bug" for now. This is how Confluence is designed - to limit image effects processing as to not overload the server. If you see this happening again consistently, please raise a new ticket and attach the image and we'll investigate further.

Hi Matt,

it might have been the load situation you described. I'll check the next time the problem occurs, as by now all images have a shadow applied.

If the effect is applied to an image and the server is not able to apply the effect on the fly, will this be done later on eg. if the page is opened under a low-load situation?

Kind regards,

Jan-Peter

Jan-Peter, can you please attach the image here that caused the issue? We'll need this to evaluate what is causing the problem.

This error message occurs when either 1) the image is too big/complex to be converted in a reasonable amount of time, or 2) the server is under load for other reasons and unable to convert images quickly. In these situations, Confluence does not apply an effect and instead shows the unadorned image in the page.