Details
-
Bug
-
Resolution: Fixed
-
Medium
-
2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 2.5.6, 2.5.7
-
Looks like a concurrency problem that is more visible on PowerPC AIX because of its memory model, but this bug applies to all platforms
-
6
-
Description
scheduled content Indexing stops possibly after manual indexing is triggered.
The very likely cause of the problem is unsynchronized access to a finished flag inside IndexingTask class.
In this class finishedReindexing flag supposed to be set once indexing is finished. However because it is not synchronized the value of the variable
may not be visible to other threads. The other code would not start indexing because it thinks that current indexing is not finished yet.
Attachments
Issue Links
- is duplicated by
-
CONFSERVER-9871 Index Queue failing to flush automatically.
- Closed
- is related to
-
CONFSERVER-10070 Indexing get stuck
- Closed
- relates to
-
CONFSERVER-9871 Index Queue failing to flush automatically.
- Closed