I assume you meant "purge"? I didn't know it was possible to "purse" a Verity collection ;)
I've seen Verity flake out on occasion - but no, I've never seen that exact error.

Oops. Um, yeah, thats purge. ;)

Been a long time since I worked with verity but in CF4.5 I had a site that would have to be purged and reindex from time to time. The cause was searches happening while large indexs were occuring. So I added locking around the index and search actions. Not sure if this is still and issue or not in CFMX7

From what I know, locking is absolutely -not- needed in CFMX7 now.

Ray,

Known problem.

See here:

http://software.groupbrowse...
http://groups.google.com/gr...
http://groups.google.com/gr...

Sami

Hi Ray.
Re your comment re locking... very interesting.

What happens if you kick off a long <cfindex> process, and then - shortly afterwards - kick it off again in a separate request (a Verity race condition, if you will).

I guess I could test this, but maybe you already know?

It's good news, anyhow.

--
Adam

Again, from what I've heard by my sources, you just don't need to worry about it. I haven't tested this yet, but I'm not seeing any locking issues. THis bug was the first oneI've run into so far.

Ray-
I'm getting the same error on one of our collections. I'd be REALLY interested in knowing if you've learned anything else about this.

We get this error pretty consistently, however.

Thanks,
Toby

Sorry Toby, but it never happaned again.

Hi Ray,

Did you ever figure out what is causing this issue? I am consistently having this issue on a couple of collections and can not find any resources on a resolution.

Thanks,

Rich

Nope. :(

Thanks Ray. I think I may need to start looking at your Lucene library if I can't figure this out. The only thing i did find is an old post that said to change the language to englishx. I have tried that and I am waiting for the collection to finish indexing. I'll post here if I find an answer or the englishx fixes it.

Rich

Yup - Just saw it in production this morning:

Steps to fix it:

Executed a 'delete' and then a 'create' on the index.
And repopulated the collection with data.

We've had numerous problems with Verity - and are even running under an unreleased patch that Adobe did for us for another issue where you ask for one collection data, and receive another's.

Good luck

Just had this happen out of nowhere today on some sites that had been running fine for months/years.

Deleting the indexes and recreating them didn't work with a fun new error. Has no one found a good solution to this yet? So far it looks like we'll be reinstalling the Verity stuff and recreating all of the indexes afterwards. Which takes forev.

If you have a lot of records or a lot of collections - I'd recommend starting to get OFF Verity as soon as possible - the problem will only get worse - my recommendation is to use Solr instead - even if you have to roll your own implementation w/o cf9.

Strangely, killing the verity service ( it wouldn't restart ) and starting it back up completely fixed the issues.

I'll ditto Kevin. Solr is the future for CF.

Was getting -1705 error from Verity after failed 'Optimize' action and when folder permissions were incorrectly set. Thinking about moving to Solr anyway.

This was frustrating me for a long time, no matter what I did I was getting the (-1705). Then I recreated the collection in cf admin and chose English (Advanced) for the language and it worked!