Bug 780316 (SOA-2722) - modeshape QueryResult.getNodes() exception
Summary: modeshape QueryResult.getNodes() exception
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2722
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0.ER7
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-29 05:09 UTC by Aleksandar Kostadinov
Modified: 2011-01-19 15:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-19 15:04:53 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 780363 0 high CLOSED modeshape sequencers glitch 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker MODE-1067 0 None None None Never
Red Hat Issue Tracker SOA-2722 0 None None None Never

Internal Links: 780363

Description Aleksandar Kostadinov 2010-12-29 05:09:56 UTC
project_key: SOA

Running a test application I have encountered an exception. I have seen it only once for now so it is not happening consistently. Calling QueryResult.getNodes() resulted in:
javax.jcr.PathNotFoundException: Unable to find "{}myfile.txt"; lowest existing path is "/"

I don't see such exception anticipated in the JCR 2 API. Please see https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-modeshape-ddl/93/artifact/jbosssoa/jboss-as/jdbc_conf/mssql2005/testapp.html or MSSQL2005 result on https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-modeshape-ddl/93/artifact/test-output/Groovy%20Test%20Suite/index.html 

Also same hudson build contains server log (https://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-modeshape-ddl/93/artifact/jbosssoa/jboss-as/server/production/log/server.log).

Comment 1 Van Halbert 2011-01-03 20:40:53 UTC
Link: Added: This issue Cloned to SOA-2726


Comment 2 Van Halbert 2011-01-04 15:19:10 UTC
Changing to blocker so further investigation can be done.

Comment 3 Anne-Louise Tangring 2011-01-04 18:26:40 UTC
Putting it for 5.1 GA, if it turns out not to be a blocker, it will be downgraded and moved to Future.


Comment 4 Dana Mison 2011-01-05 00:08:16 UTC
Writer: Added: Darrin


Comment 5 Randall Hauch 2011-01-05 22:18:20 UTC
I believe this has been fixed in ModeShape (in the trunk and 2.2.x branch). As I mentioned in MODE-1067, I wasn't able to replicate the error (it is timing related), but I do think the failure mechanism and fix were straightforward.

Comment 6 Aleksandar Kostadinov 2011-01-06 06:13:58 UTC
Thanks! Once I have the patch into a release I'll try to run test continuously to hopefully fall into same situation. My guess is my test program will fail in a different way which should prove your fix is correct (or not).

Comment 7 Van Halbert 2011-01-08 19:37:32 UTC
A fix was committed to the 2.2.x product branch.   However, it was indicated that problem was not able to be duplicated, but they feel the patch addresses a symptom of the problem after performing a code review and fixing 2 of the 3 access patterns.

Comment 8 Aleksandar Kostadinov 2011-01-16 17:22:20 UTC
Link: Added: This issue is related to SOA-2772


Comment 9 Aleksandar Kostadinov 2011-01-19 15:04:53 UTC
Based on numerous test repeats and also on the tests I have run for SOA-2772 I am pretty confident this issue has been resolved.


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