tracker issue : CF-4165678

select a category, or use search below
(searches all categories and all time range)

Sequential cfindex operations may report a wrong status

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Alexandre Potvin Latreille / Alexandre Potvin Latreille (Alexandre Potvin Latreille)

Created: 06/17/2016

Components: Text Search, Solr

Versions: 11.0

Failure Type: Incorrect w/Workaround

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Normal / Some users will encounter

Locale/System: ALL / Win 2008 Server R2

Vote Count: 1

Listed in the version 2016.0.03.300466 Issues Fixed doc
Problem Description: Quickly performing (cfindex action=update) and (cfindex action=delete) operations sequentially on the same thread may result in an incorrect status being reported.

Steps to Reproduce:

1.Do cfindex action=update with a query.
2.Do cfindex action=delete with a query and store the status using the 'status' attribute.

Actual Result: The status reported from the second operation may be wrong. For instance, the delete count may be wrong, being sometimes even greater than the number of keys deleted.

Expected Result: The status should be properly reported.

Any Workarounds: I noticed that if I add a long-enough <cfset sleep(...)> between both operations then the status will be properly reported, but that is quite unreliable.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4165678

External Customer Info:
External Company:  
External Customer Name: Alexandre Potvin Latreille
External Customer Email:  
External Test Config: My Hardware and Environment details:



I see the same thing, usually with the delete count being reported as zero when it should be one. Win 2008 R2 with CF11.
Comment by External U.
2369 | July 11, 2016 06:34:49 PM GMT
Just to make sure, in which build was this fixed?
Comment by External U.
2370 | November 04, 2016 12:05:55 PM GMT
I am on Version 11,0,08,298512 and still see the error.
Comment by External U.
2371 | November 04, 2016 12:12:35 PM GMT