Hi,
We have a standalone transformation server, and for big (1000 page) PDFs we noticed it was timing out at 120seconds.
Now, the values seemed to be hardcoded into an xml file on the TS server and I edited them, and now we have transformations that can take up to 10 mins for the large files.
Also, transformserver.transformationTimeout=600 was set in the global properties, as well as content.transformer.default.timeoutMs=600000 just in case.
HOWEVER, there is a stupidly strange problem, although the transformations actually succeed, Alfreso seems to send another transformation request to the TS server every 2 mins, and we end up with 4 transformations done for each of these large files.
Has anyone come accross this before? Is there some 120s timeout I am missing somewhere?
Could the share front end be resending the request after it times out after 120s and generating another Transform request to the repo boxes which then forward that on to the TS box?
Its really really frustrating, and we dont seem to be getting anywhere with this issue.
Now normaly the man with a plan is Mrogers, I am hoping you read this and can give me your expert opinion of how people are dealing with super large PDFs. In our case its around 70Mb, and 1000 pages.
Thanks!
