CFCOLLECTION timeouit issue

I have an automated process which refreshes a collection at midnight everyday, many files can be uploaded in a day, so the collection is built/rebuilt on off hours. been running for over a year but last few days have been getting a timeout in the cf log

system is CF5

is there a max size for processing a collection?
one directory being set for the collection is 1375 files totalling 734M of mixed file types, mainly PDF oterh directory being scanned has 998 files totaling 735M, again mainly PDF files

what limitations does the cfcollection have regarding number of files and or max processing size?
LVL 25
James RodgersWeb Applications DeveloperAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Mr_NilConnect With a Mentor Commented:
To be honest - if your request is running to 17+ minutes then adding a cfsetting won't make any difference.

Does the task complete if you run it manually?

Can you still search the collection?

Have you tried deleting/remove/obliterating the existing collection and recreating it from scratch?
Its been a long time since I worked with CF5 and Verity, but I vaguely recall there being times where the collection would get corrupt, but you wouldn't necessarily know this had happened and indexing would seem to take forever.

I was about to suggest adding the update to the end of the file upload (as you mention) but to wrap it in cfthread, so that it can go off and run in the background.  But then I remembered that this is CF5 we're talking about.... :/  

0
 
Mr_NilCommented:
K2 restrictions on CF5 were :
    * For ColdFusion Professional, K2 Server can search a maximum of 125,000 documents.
    * For ColdFusion Enterprise, K2 Server can search a maximum of 250,000 documents.


Have you tried adding a cfsetting requesttimeout in the template?

What does the time out error point to in your script? Is it cfindex or cfcollection?  If its cfcollection what action are you undertaking?
0
 
James RodgersWeb Applications DeveloperAuthor Commented:
i moved the site giving the error to a new local environment to see if i could duplicate the error locally before working on a solution for the production environment , i set up the local system with the same parameters, time, files, processes and pathways as the original system, it ran last night and i got this error

1min and 51 seconds in to the routine i get
!!  CFTrace::logThread(18780) has no entry for thread 18780

A request exceeded the timeout. The unresponsive thread count is up to 2. [Drive:\server\sitename\website\path\search\createVerityCollection.cfm]

17 minutes and 26 seconds after routine starts i get
A long-running request returned. The unresponsive thread count is down to 1. [Drive:\server\sitename\website\path\search\createVerityCollection.cfm].

and at 17:28
A long-running request returned. The unresponsive thread count is down to 0. [C:\CFusion\Scripts\cfexectask.cfm].



createVerityCollection.cfm is a group of commands and checks to determine if the collection already exists and to perform accordingly - make it if it doesn't, purge and update if it does, it has been running for over a year and is now having timeout issues

one option was to append the collection with each upload, problem is the users sometimes update the files, as much as 10 times in a day

>>Have you tried adding a cfsetting requesttimeout in the template?
that is only a hot fix i think and does not address the underlying issue, i could do it but next week/month if i start getting the same issue then i didn't really solve the problem and i'll be back to the beginning looking for the error/issue
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.