Thanks for the info, Dan. We have projects in the queue to move to categories, but like all queues, we won't get to it until we get to it (or until someone makes is a /much/ bigger priority than it is right now). I was hoping to find a quick fix. I'll take a look at what I have in the way of locks and any of your other suggestions.
Thanks again. On 4/25/06, Dan G. Switzer, II <[EMAIL PROTECTED]> wrote: > Rob, > > >Is anyone aware of a Verity limitation in MX7? I know there were > >extreme changes, but I have an application that indexes multiple > >collections simultaneously by kicking off each index on a separate > >thread. Essentially, one template is called which loops over the > >available collections and creates a new thread for each which handles > >the actual indexing. This worked great through MX6.1, but now with > >MX7 it's failing with the following message: > > > >An error occurred while performing an operation in the Search Engine > >library. > >Error reading collection information: > >com.verity.api.administration.ConfigurationException: > >java.io.IOException: Read timed out > > > >The error appears to be returned very quickly after the indexing > >process has started and the failure notice is received for all > >collections. Anyone have any thoughts? I'd hate to have to serialize > >the indexing process because some collections are large and there may > >be a number of them. > > > >Any insight would be greatly appreciated. > > I've been fooling around quite a bit w/Verity in CFMX 7 Standard as of late. > It's really slow when you have lots of collections. How many total > collections do you have? We have over 60 different collections and it takes > Verity about 30 sections to index a single database item (although I think > this has more to do w/checking to make sure the collection exists.) > > First, I'd recommend moving to using catagories instead of individual > collections--which were introduced in CFMX 7. Unlike previous versions of > Verity in CF, all the collections are now loaded and kept in memory. If you > have a bunch of collections, you can find yourself very quickly running out > of RAM and moving to using virtual memory--which kills performance. Using > the categories in Verity should drastically reduce the memory requirements > of Verity. > > Next, you might be better off firing off an async event that does all the > indexing in sequence--instead of firing off a new thread for each indexing. > > Also, I'd remove <cflock />'s around your <cfindex /> and <cfsearch /> tags, > as the usuage of locks has been depreciated. > > -Dan > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:238709 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
