[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128125#comment-15128125
]
Julian Reschke commented on OAK-3937:
-
So what I currently see (not nicely reproducable) is:
java.lang.AssertionError: expected null, but was:<1:/node-10>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotNull(Assert.java:755)
at org.junit.Assert.assertNull(Assert.java:737)
at org.junit.Assert.assertNull(Assert.java:747)
at
org.apache.jackrabbit.oak.plugins.document.MultiDocumentStoreTest.concurrentBatchUpdate(MultiDocumentStoreTest.java:288)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
and this happens for PostgreSQL and H2.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.3.15
>
> Attachments: OAK-3937.diff, OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128094#comment-15128094
]
Julian Reschke commented on OAK-3937:
-
Still seeing failures; now trying with the patch for OAK-3959 as well. (cc:
[~tomek.rekawek])
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.3.15
>
> Attachments: OAK-3937.diff, OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15128299#comment-15128299
]
Julian Reschke commented on OAK-3937:
-
See also https://github.com/pgjdbc/pgjdbc/issues/502
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.3.15
>
> Attachments: OAK-3937.diff, OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126296#comment-15126296
]
Julian Reschke commented on OAK-3937:
-
Observation: {MultiDocumentStoreTest.concurrentBatchUpdate()} fails both for
PostgreSQL and DB2.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126343#comment-15126343
]
Tomek Rękawek commented on OAK-3937:
Does it fail on the current trunk or the trunk+patch? On my machine DB2 passes
this test everywhere and the PostgreSQL passes it on the patched Oak.
What driver & DB2 server do you use? For me it's {{com.ibm.db2:db2:4.16.53}}
and DB2 {{v10.5.0.5}}.
Does your DB2 passes all tests in rdb-oddity.patch?
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126371#comment-15126371
]
Julian Reschke commented on OAK-3937:
-
Currently, the failure is gone (dunno why). Will keep you posted.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126443#comment-15126443
]
Tomek Rękawek commented on OAK-3937:
Great insight! Could you check if the patch from OAK-3959 affects this somehow?
It sets the upsert flag to true for all bulk update retries.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126661#comment-15126661
]
Julian Reschke commented on OAK-3937:
-
Turns out I have a typo in my patch; please excuse the prior noise.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.diff, OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15126530#comment-15126530
]
Julian Reschke commented on OAK-3937:
-
I think the patch helps as well, but I still see random failures (MySQL) and
deadlocks (MSSql).
There's definitively something else that needs to be fixed as well.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
>Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125327#comment-15125327
]
Tomek Rękawek commented on OAK-3937:
The attached patch enables autoCommit for the bulk UPDATE method (not for the
bulk INSERT). It also removes one redundant commit() (invoked after a batch
SELECT operation).
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
> Fix For: 1.4
>
> Attachments: OAK-3937.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125371#comment-15125371
]
Tomek Rękawek commented on OAK-3937:
My observation is that on the PostgreSQL, if we have a bulk INSERT and there's
a conflict, the {{BatchUpdateException#getUpdateCounts}} returns positive
update count even for rows that haven't been successfully created. Attached
patch ignores the {{BatchUpdateException#getUpdateCounts}} values on PostgreSQL.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
> Fix For: 1.4
>
> Attachments: OAK-3937.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OAK-3937) Batch createOrUpdate() may fail with primary key violation
[
https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123799#comment-15123799
]
Tomek Rękawek commented on OAK-3937:
It seems that in the current trunk the problem only exists on the PostgreSQL.
It can be fixed with setting autoCommit() for the bulk update connection.
> Batch createOrUpdate() may fail with primary key violation
> --
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
>Reporter: Marcel Reutegger
> Fix For: 1.4
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a
> primary key violation exception.
> {noformat}
> java.lang.AssertionError:
> org.apache.jackrabbit.oak.plugins.document.DocumentStoreException:
> org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation:
> "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL
> statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT,
> CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test
> {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
