I see some inconsistency in persisting repository contents and/or querying it. I'm running a simple application that basically puts a file node into a newly created repository and then queries for it and eventually removes the node.

Usually all operations execute fine but sometimes these fail. I'm running tests against multiple database servers. You can see test results on https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-modeshape-ddl/92/artifact/test-output/Groovy%20Test%20Suite/index.html

Please ignore DB2 as it fails anyways for other reasons.

Basically the file node is inserved, the session has its save() method invoked but subsequent queries are not seeing the file node. You can see the index.jsp that is used to perform the repository operations at https://svn.devel.redhat.com/repos/jboss-qa/hudson/config_repository/resources/soa/modeshape/basic-repo-test.war/index.jsp

My wild guess is that the save() operation returns before changes are actually persisted in the DB thus queries don't see the file node. Or could that be something with caching? I'm sure that file is eventually persisted into the database because I see it looking at the MODE_SIMPLE_NODE database table. I don't know what spec says wrt seeing your changes after a save() call if it is specified at all. But IMHO such behavior could be confusing.

I've seen this problem with some previous ERs once or twice but since there were a couple of other bugs within them, this didn't catch my attention. Looking at my previous builds I spotted one that happened with the preconfigured "eds" repository. Note that index.jsp there is an earlier version also. (https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-modeshape-ddl/73/ look at "eds" test only)