Bug 780175 (SOA-2550) - ModeShape VDB and ModeShape-JDBC does not show records created with JCR API under specific conditions
Summary: ModeShape VDB and ModeShape-JDBC does not show records created with JCR API u...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2550
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0.ER4
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-08 09:38 UTC by Jiri Pechanec
Modified: 2011-01-11 10:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-11 10:44:43 UTC
Type: Bug


Attachments (Terms of Use)
QueryTest.java (4.86 KB, text/plain)
2010-11-08 09:40 UTC, Jiri Pechanec
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2550 0 Critical Closed ModeShape VDB and ModeShape-JDBC does not show records created with JCR API under specific conditions 2013-04-04 00:31:04 UTC

Description Jiri Pechanec 2010-11-08 09:38:45 UTC
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.

Comment 1 Jiri Pechanec 2010-11-08 09:40:01 UTC
Attachment: Added: QueryTest.java


Comment 2 Anne-Louise Tangring 2010-11-09 16:11:00 UTC
Candidate for SOA 5.1.0

Comment 3 Van Halbert 2010-11-09 20:09:32 UTC
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.

Comment 4 Van Halbert 2010-11-17 21:31:32 UTC
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.

Comment 5 Jiri Pechanec 2011-01-11 10:44:43 UTC
Verified in ER6


Note You need to log in before you can comment on or make changes to this bug.