499 timeouts when viewing details on a large Group Review and Approve Workflow

[throwback]

Hi Y'all,

So I've done a slightly dumb thing- assigned a Group Review and Approve Workflow to a group containing 300 odd users. All seems to be working great, apart from when I view the details of the workflow in the "Workflows I've started" dashboard I get a generic "Failure" message after 120s. Other large group workflows (not quite so large) I've created work, they just take some time to display the details. So I reckon this is just an internal time-out - I figure if I can increase the timeout I can just wait and eventually Alfresco will compose the view details page correctly.

The errors I'm getting in the logs are attached, as well as a screenshot (ok, forum won't let me post that, but its just the view details page, blank, with "failure" bang in the middle of it) showing corresponding error in the Share web interface.

I found the following bug on JIRA with a similar error, but I’m not sure how to define the timeout described in the fix- cannot find the corresponding config file in Alfresco 4.0.d:  https://issues.alfresco.com/jira/browse/ALF-10737

I would consider upgrade to 4.2.c to see if this resolves, but we make extensive use of the Sharepoint integration and it is just too broken in 4.2.x for us to use, so we are holding out for a later release. Running test environments in both. Would be handy to figure out how to tweak this timeout to let me get the workflow status out in a coherent format without arguing with workflow console/pulling data through sql queries.

Any ideas anyone how I can increase the timeout "2013-03-08 16:36:09,974  INFO  [webscripts.connector.RemoteClient] [http-8080-25] Error status 499 Read timed out" so I can give Alfresco time to complete building the view details page?

Kind regards,

Iain Bagnall

[afaust]

Hello,

the JIRA ticket you reference already contains the information you need to increase the timeout. Create a custom-slingshot-application-context.xml in your /alfresco/web-extension/ and override the default remote client bean. E.g.:

<blockcode>
<bean id="connector.remoteclient" parent="connector.remoteclient.abstract" class="org.alfresco.web.scripts.SlingshotRemoteClient" scope="prototype">
   <!– Twice the default timeout of 2 minutes –>
   <property name="readTimeout" value="240000" />
</bean>
</blockcode>

Regards
Axel

[throwback]

Hi Axel,

Danke - job done! Had to omit the scope="prototype" as it threw up errors when I included this (I think to do with the schema declaration used in the default sample file, scope is only supported by spring 2.0?), otherwise this has done the job. Didn't realise that config had to go into "custom-slingshot-application-context.xml". You learn something new every day…

Thank you for your kind assistance.

Kind regards,

Iain