Details
-
Bug
-
Resolution: Tracked Elsewhere
-
High
-
None
-
4.2.13, 4.3.7, 5.0.2, 5.1.3
-
None
Description
Customers who are running Confluence 4.3.x are finding that their indexing becomes broken when Team Calendars v3.2.3 is enabled in their instance. The index appears to run successful but refreshing the page suggests that the Index isn't rebuilt, even though they have just run the process.
Looking in the atlassian-confluence logs, a very distinct error is shown:
2013-06-13 13:50:05,471 ERROR [Indexer: 8] [confluence.search.lucene.ReindexWorkBatch] indexCollection Error indexing document -- referer: http://localhost:6430/admin/search-indexes.action | url: /admin/reindex.action | userName: admin | action: reindex java.lang.NoClassDefFoundError: Could not initialize class com.atlassian.confluence.index.Lucene29FieldDescriptorMapper at com.atlassian.labs.lucenecompat.impl.Lucene29AdaptingExtractor.<init>(Lucene29AdaptingExtractor.java:28) at com.atlassian.labs.lucenecompat.impl.Lucene29ExtractorFactory.convert(Lucene29ExtractorFactory.java:16) at com.atlassian.labs.lucenecompat.spring.DynamicExtractorModuleDescriptorsFactory$CompatibilityExtractor.addFields(DynamicExtractorModuleDescriptorsFactory.java:154) at com.atlassian.bonnie.search.BaseDocumentBuilder.getDocument(BaseDocumentBuilder.java:104) at com.atlassian.confluence.search.lucene.ConfluenceDocumentBuilder.getDocument(ConfluenceDocumentBuilder.java:97) at com.atlassian.confluence.search.lucene.tasks.AddDocumentIndexTask.perform(AddDocumentIndexTask.java:43) at com.atlassian.bonnie.index.TempIndexWriter.perform(TempIndexWriter.java:73) at com.atlassian.confluence.search.lucene.TempIndexWriterStrategy.perform(TempIndexWriterStrategy.java:43) at com.atlassian.confluence.search.lucene.tasks.TempIndexBackedIndexTaskPerformer.perform(TempIndexBackedIndexTaskPerformer.java:21) at com.atlassian.confluence.search.lucene.ReindexWorkBatch.indexCollection(ReindexWorkBatch.java:125) at com.atlassian.confluence.search.lucene.ReindexWorkBatch$1.doInTransaction(ReindexWorkBatch.java:86) at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128) at com.atlassian.confluence.search.lucene.ReindexWorkBatch.run(ReindexWorkBatch.java:56) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680)
WORKAROUND:
- Downgrade the plugin to the previous version by removing it from the database by following the instructions in this document to remove the plugin from the database: https://confluence.atlassian.com/display/DOC/Removing+Malfunctioning+Add-ons
- After this you should flush the plugin caches by performing the steps outlined in this document: https://confluence.atlassian.com/display/CONFKB/How+to+Clear+Confluence+Plugins+Cache
- You can then reinstall v3.2.2 of the plugin, found on this link: https://marketplace.atlassian.com/plugins/com.atlassian.confluence.extra.team-calendars/versions
- Finally, you will need to rebuild the index from scratch by following the instructions in this document: https://confluence.atlassian.com/display/CONFKB/Rebuild+the+Content+Indices+from+Scratch
NOTE: Whenever making changes in the database you should ALWAYS backup your data before proceeding!
The problem will be fixed for Team Calendars 3.2.4
Attachments
Issue Links
- is caused by
-
-
- Closed
-
