I stand corrected. =native did NOT solve the write.lock error.
Do we need to make sure no write.lock file exists after app server shutdown?
Does that parameter belong in the persistence unit instead of env?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Re-indexing and overwriting index folder causes errors | 4 | 2680 | March 11, 2019 | |
| LockObtainFailedException with gradle test after v6.1 migration from 5.x | 6 | 492 | January 26, 2023 | |
| Lucene index corruption | 7 | 3535 | May 2, 2019 | |
| Search indexes not being created in aws | 1 | 947 | April 23, 2018 | |
| Clarification/Confirmation of Shared Lucene index folder | 6 | 1078 | February 1, 2018 |