Bug 779962 (SOA-2322) - Repository engine call hangs when getting federated repository
Summary: Repository engine call hangs when getting federated repository
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2322
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-16 09:38 UTC by Jiri Pechanec
Modified: 2010-10-01 15:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-01 15:54:47 UTC
Type: Bug

Attachments (Terms of Use)
modeshape-config.xml (11.66 KB, text/xml)
2010-09-16 09:40 UTC, Jiri Pechanec 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2322 0 None None None Never

Description Jiri Pechanec 2010-09-16 09:38:54 UTC 
project_key: SOA

See attached Modeshape configuration file.  JcrConfiguration is loaded, JcrEngine started and call engine.getRepository("repository-federated") hangs indefinitely.
Comment 1 Jiri Pechanec 2010-09-16 09:40:02 UTC 
Attachment: Added: modeshape-config.xml
Comment 2 Van Halbert 2010-09-16 15:21:44 UTC 
Are you starting another JcrEngine in the VM?    Also, can you attach the server log?
Comment 3 Van Halbert 2010-09-16 20:29:06 UTC 
Link: Added: This issue depends MODE-900
Comment 4 Jiri Pechanec 2010-09-17 06:25:10 UTC 
I am using the rpoeisotry not in AS but outside - thus there are no AS logs. I am starting only one JcrEngine in the test
Comment 5 Van Halbert 2010-09-23 13:59:50 UTC 
Engineer comment: 

As for the problem configuration file: it looks like the projections in the federated repository use "&gt" rather than '>', and this would definitely cause a problem.
Comment 6 Jiri Pechanec 2010-09-24 06:33:29 UTC 
Using > would mean to generate invalid XML so ModeShape should handle proper XML as well
Comment 8 Van Halbert 2010-10-01 15:54:47 UTC 
ModeShape has fixed the issue and checked the changes into the 2.2.x branch, which will be in the next pull for a build.
Note You need to log in before you can comment on or make changes to this bug.