We use the verity collections to index our databases for faster searches.

However, when our indexing program runs (see below), we run into the seefusion timeout error.

We have tried using the requesttimeout=3500, but seefusion ignores the requesttimeout.

How can we get around the timeout for procedures that exceed the seefusion timeout?

Thanks.

<cfindex action="UPDATE"
collection="#collectionnamea#"
key="page_number"
type="CUSTOM"
title="headline"
query="get_db_info"
body="html,headline,byline"
custom1="access"
custom2="alternate_link">

Bill,

There is no way to get around SeeFusion. It is set to kill requests that take longer than 50 seconds to complete.

To work around this -- I would suggest breaking your verity up into smaller parts/multiple collections.

This way the collection can index in the given time-frame.

Please contact support with any questions. Thank you!

To clarify this a bit, the reason why you can't get around the timeout is that it would defeat it's purpose to do so. I admit that in some respects this seems like a limitation, but we tested extensively and the timeout being used now is the highest we can allow that shows a marked increase in performance on a shared CF Server.

If the timeout is killing your app the first thought should be to recode as Josh suggested. If your app uses a DB then you should considered strengthening the queries you're using and making sure your DB is setup optimally (i.e. indexed, etc.)

Finally, when all else fails and you've acknowledged that there is no possible way to shorten your execution time, consider moving to a VPS account since they don't run SeeFusion on the premise that if you crash CF with your code on one of those then your sites are the only ones affected.