-
Bug
-
Resolution: Done
-
Blocker
-
3.1.3.Final
-
None
When creating nodes under explicit JTA transaction, it took much more time to save compared to non transaction.
When query functionality is disabled, the time spent in both cases are almost identical (In my real case, the transaction case even run a little bit faster than non transaction case). Therefore, I think it should be a Hibernate Search/Lucence integration issue.
See attached profile data for details
In the non-transaction case, there are 8 [Lucene Merge Thread] threads created.
However, in the transaction case, there are 89 [Lucene Merge Thread] threads created which almost ten times than previous case.
- blocks
-
MODE-1837 Sometimes query returns duplicated records after commiting a transaction that contains VersionManager.checkin() call when using a real JTA transaction manager
- Closed
- is related to
-
MODE-1822 VersionManager.checkin throws exception in the transaction when using JTA transaction manager
- Closed
-
MODE-1837 Sometimes query returns duplicated records after commiting a transaction that contains VersionManager.checkin() call when using a real JTA transaction manager
- Closed