Hi, after a lot of debugging in Oak source code, removing all additional code we mounted around Oak (management of many repositories, encryption, external authentication, text extraction, user management, etc) and even mounting from scratch a working example. I finally found the problem. It was a static piece of code, related to Aspose. That static piece of code was in a custom tika parser (configured to be used in text extraction). When I removed that static initialization, indexes in affected repositories returned to normal, I can't tell the exact reason for that. Anyway, thanks.
El jue, 9 may 2024 a las 14:22, Jorge Flórez (<[email protected]>) escribió: > Hi, > > I don't know if this is related to the problem we are having: > > 2024-05-09 13:50:00,316 WARN > [org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate] > (oak-scheduled-executor-3) [async] No reference checkpoint set in index > stats > > Could this "reference point not set" be the root of all my problems? > > El lun, 29 abr 2024 a las 16:24, Jorge Flórez (< > [email protected]>) escribió: > >> Although it seems to process the index, it appears it does not "mark" the >> index as processed, every time I start the server, the indexing process >> starts again, very odd. >> >> El lun, 29 abr 2024 a las 10:58, Jorge Flórez (< >> [email protected]>) escribió: >> >>> Hi all, >>> >>> I am having a little problem, we are using Oak 1.52.0, packaged in a >>> war, that is deployed on Wildlfy 24. When I insert an index using >>> >>> Node indexesParentNode = session.getNode("/oak:index"); >>> Node indexNode = >>> indexesParentNode.addNode("test","oak:QueryIndexDefinition"); >>> <node structure creation> >>> session.save(); >>> >>> the async indexer seems not working, nothing is registered in my log. >>> Same thing happens when I try to reindex using >>> >>> Node indexesParentNode = session.getNode("/oak:index"); >>> Node indexNode = indexesParentNode.getNode("test"); >>> indexNode.setProperty("reindex", true); >>> session.save(); >>> >>> The log shows nothing. >>> >>> Any ideas what could be causing this? In previous Oak versions we did >>> not have any problems creating (or reindexing) indexes. >>> >>> PS: When I restart Wildfly or redeploy my war I see >>> (async-index-update-async) Reindexing will be performed for following >>> indexes: [/oak:index/test] >>> (async-index-update-async) Estimated node count to be traversed for >>> reindexing under / is [10240] >>> (async-index-update-async) reindexCompletionTimestamp set to current >>> time for index:/oak:index/test >>> >>> So it may be doing something, but just at the beginning. >>> >>> Thanks. >>> >>> Jorge >>> >>>
