Our FTS Process Queue task has been failing for over a week now with the same error (see attached file). It appears that the indexer has enabled some sort of file lock but never released it.
What is the best approach for removing this lock and how do we determine the root cause of this lock not being removed? Restarting the server requires us to go through a pretty extensive request process and can be rather time consuming so I would prefer to avoid restarting Tomcat if at all possible.
Any help is greatly appreciated. Thank you,
Corey Amoruso
Hi,
Could you please provide more information about your problem? Which version of the platform do you use?
Could you please check that this problem still reproduces on the newest version of the platform? Also, it will be helpful if you share a small sample project along with reproduction scenario that demonstrates the issue.
This solution is currently running on Cuba Platform version 6.7.12. We are not sure what the root cause of the issue is. It seems like the Lucene Indexer was perhaps interrupted somehow and left in a bad state. I did a little more reading and this seems to happen when the Lucene indexer is stopped before calling its’ close method leaving a lock on the indexes it is building. I have seen some solutions proposed elsewhere requiring to manually call the close method for the indexer. We are going to be performing a restart of the Tomcat service on Friday to see if that solves the issue.
Would it be possible to get a JMX command to manually close the Lucene indexer from the front end of Cuba? This would prevent the need for a Tomcat restart should the indexer get interrupted for any reason.
Great, thank you. We are planning on upgrading to the 6.9 version in a few months. Until then will a restart of Tomcat resolve this error and allow FTS to continue?