mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git

Jean-Noel Rouvignac
10.07.2015 3df9a0cef805b4f35fd6e4a7d6dc18701b72762e
refs
author Jean-Noel Rouvignac <jean-noel.rouvignac@forgerock.com>
Friday, April 10, 2015 11:07 +0200
committer Jean-Noel Rouvignac <jean-noel.rouvignac@forgerock.com>
Friday, April 10, 2015 11:07 +0200
commit3df9a0cef805b4f35fd6e4a7d6dc18701b72762e
tree 618ee887e40ed227f48a9bb97a395dcaa8da89eb tree | zip | gz
parent 897c4335fde7e69c72930d3432b203efaa681ba9 view | diff
OPENDJ-1893 (CR-6600) Do not hardcode Importer threadCount to 1

Problem was due to multiple threads sharing the same Persistit exchanges. Generally speaking DBs do not like mixing transactions and threads.
By using transactions for each DB access, the problem disappears.
Are we losing any performance by using full fledged transactions? Could we somehow do these operations in a thread safe manner without the need to use transactions?

Importer.java:
Use transactions for read/write operations on DN cache.
1 files modified
143 ■■■■■ changed files
opendj-sdk/opendj-server-legacy/src/main/java/org/opends/server/backends/pluggable/Importer.java 143 ●●●●● diff | view | raw | blame | history