Hide Forgot
project_key: SOA See attached test file It creates a node '/queryNode'. Test testSelectUsingVDB() tries to retrive the node to verify that ModeShape.vdb is present and responsive. After server startup when the test is executed in separate process it fails with java.lang.AssertionError: More than one record should be present in repository expected:<false> but was:<true> If the test is executed in the same process as the server then the testSelectUsingVDB() passes but test testSelectUsingModeShapeDriver() fails with java.sql.SQLException: Current row not set at org.modeshape.jdbc.JcrResultSet.isRowSet(JcrResultSet.java:1347) at org.modeshape.jdbc.JcrResultSet.getValueReturn(JcrResultSet.java:1176) at org.modeshape.jdbc.JcrResultSet.getString(JcrResultSet.java:1016) at org.modeshape.jdbc.JcrResultSet.getString(JcrResultSet.java:1006) at org.jboss.resource.adapter.jdbc.WrappedResultSet.getString(WrappedResultSet.java:875) at org.jboss.soa.modeshape.qa.tests.QueryTest.runSQLQuery(QueryTest.java:88) at org.jboss.soa.modeshape.qa.tests.QueryTest.testSelectUsingModeShapeDriver(QueryTest.java:103) If the test is executed second time all tests passes. Then if the testSelectUsingVDB() is executed in separate process then it passes every time. Can the issue be linked to transaction isolation levels? Config file is used as it comes with ER3.
Attachment: Added: QueryTest.java
Candidate for SOA 5.1.0
Can I get this retested in ER4 because with this release, sessions are handled differently (and hopefully better), which has direct impact on what information is available.
This needs to be retested in ER4 because of the changes that directly related to how sessions are handled and that impacts what data is available when queried.
Verified in ER6