JCR Session not seeing changes made on a different thread when using ModeShape 4.1.0.Final

[ma6rl]

I updated from 4.0.0.Final to 4.1.0.Final this morning and a number of my unit tests have started failing.

The problem appears to be the changes made in session b on a different thread are no longer visible to session a. Below is the sequence of events:

session a created

JTA transaction started

session a creates node

session a saves node

JTA transaction committed

session b created

JTA transaction started

session b updates node

session b saves

JTA transaction committed

session a gets node

session a sees old version of node prior to session b's changes

This has been working fine since Alpha1. Is this an expected change and or should I raise an issue in JIRA?

Thanks.

[hchiorean]

Assuming you're using READ_COMMITTED isolation with PESSIMISTIC locking in Infinispan, please raise a JIRA as long as you can provide a test case.

We have several tests - both for standalone & WF (modeshape/TransactionsTest.java at master · ModeShape/modeshape · GitHub and modeshape/TransactionsTest.java at master · ModeShape/modeshape · GitHub), so whatever this is, it's not straightforward. Thanks.

[ma6rl]

hchiorean I've created [MODE-2395] JCR Session not seeing changes made on a different thread when using ModeShape 4.1.0.Final - JBoss Issue Tra… to track the issue and attached a PR with an Arquillian Test that can be used to re-create it.

Re-creating it was by no means straight forward and this is most definitely an edge case but it is breaking a number of my integration tests so I would really appreciate help in tracking it down.

Thanks.