Bug 780968 (SOA-3439)
| Summary: | modeshape sequencing performance predictability | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Aleksandar Kostadinov <akostadinov> | ||||||
| Component: | ModeShape | Assignee: | Van Halbert <vhalbert> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | unspecified | CC: | akostadinov, akostadi, fnguyen, ldimaggi, soa-p-jira, vhalbert | ||||||
| Target Milestone: | ER1 | ||||||||
| Target Release: | 6.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-3439 | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
Previously, use of timeouts with asynchronous sequencers was resulting in unexpected behavior. In this version of JBoss Data Virtualization you can register a JCR event listener for ModeShape events, including for completion of sequencing operations.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-03-10 20:29:42 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Aleksandar Kostadinov
2011-10-05 14:43:33 UTC
Link: Added: This issue Cloned to SOA-3440 Attachment: Added: sequencer_csv.jsp Retry with attached sequencer_csv.jsp. It contains changes to the logic where iterating over the nodes and re-executing the query. If an issue is still found, please reopen. As I commented in MODE-1276, does spec allow reordering of operations? I mean is the cause of the problem I see and is it a feature or a bug? Labels: Added: modeshape Having a the code changed to make things work for me is not a prove there is no problem with modeshape. Is there anything in the test code that goes against specifications? If yes, then please point that out and close the issue. If not then I think this bug needs to be taken seriously. Moving to SOA 6, because this is when it was agreed ModeShape's 3.0 version and its revamp of its internal architecture will produce the performance improvements that cannot be made on a ModeShape 2.x branch for SOA 5.x. I can confirm that in SOA 6 (ModeShape 3.x), I will be possible to be notified when a sequencing operation is finished by registering a JCR event listener for a ModeShape specific event. This means that there will no need for variable waits & timeouts. Horia, would you kindly provide a patch for sequencer_csv.jsp for using this feature? That can then be used in the test runs. Looking at the JIRA issue, Randall is referring to the synchronous feature which is not yet implemented (will be in 3.3). I will provide the patch once the feature is implemented. I meant the JCR event listener solution. Async handling is fine as long as we have a reasonable way to know when sequencing finished to test the resulting repo state. Created attachment 687448 [details]
Updated sequencer jsp with event handling
Attached an updated jsp file together with the repository config I used for testing. The relevant part of the sequencing listener is between lines #112 and #142.
Please note that the original jsp attached is broken: doesn't compile out-of-the-box and in the case of the final check (if (i==100)) never terminates, causing a potential infinite loop.
Fixed before GA - setting to requires_doc_text- accordingly JCR event listener solution is used throughout our test suite. |