| Summary: | org.drools.reteoo.SchedulerTest.testDoLoopScheduledActivation failing on HP JVM (ia64) | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Lukáš Petrovický <lpetrovi> |
| Component: | Documentation | Assignee: | Dana Mison <dmison> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3 IR4 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.3 CP01 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-814 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-03-17 12:28:36 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 778604, 778704 | ||
|
Description
Lukáš Petrovický
2008-09-22 11:05:52 UTC
Link: Added: This issue depends JBRULES-1777 From MarkP: "The schedular tests are dependant on delays, before doing the assertion, maybe the GC on the HP machines takes longer than expected. Has anyone tried just extending the wait time?" From Mic: "The duration feature is only suitable for desktop applications. For server resident apps (ie most likely what you are building) there are better options for long running state and timing. In other words, do not use this feature on a server". Emailed Jervis for comments For info, the response from Jervis. "Hi Neil, the conclusion guys have reached is that we wont fix this jira but a release note instead. I will forward relevant email threads to you in a separate email." Component changed from JBoss-rules to documentation. When I've got the emails I'll re-assign to darrin. Checked up on this and the answer is to put the line from September into the release notes. "The duration feature is only suitable for desktop applications. For server resident apps (ie most likely what you are building) there are better options for long running state and timing. In other words, do not use this feature on a server". Link: Added: This issue is a dependency of SOA-1077 I need more information to document this, specifically: The "duration feature" of what ? and what are the better options ? Link: Added: This issue is a dependency of SOA-1168 Added to Known Issues: The rule attribute "duration" should not be used for the timing of long running server processes. Over long time frames with many processes, minor variations in timing on different JVM, OS and hardware implementations can compound to produce inaccurate results. This is not a factor for desktop applications. Additional information: https://jira.jboss.org/jira/browse/JBRULES-1777 Assigning to QE to verify that the change is (also) in the 4.3 CP01 docs. I can't see the change in the release note doc here: https://svn.devel.redhat.com/repos/jboss-soa/branches/4.3/build-tools/docs/esb/ https://svn.devel.redhat.com/repos/jboss-soa/branches/4.3/build-tools/docs/esb/4.3.CP01_Release_Notes.pdf As or March 3 I set it to resolved when I updated the content in the xml source & committed it. But I didn't rebuild the pdf and commit it again since there was still a lot more to do for that doc with other JIRAs. Release Notes have been submitted for QE, see SOA-1168 The changes are not in the doc here: Revision 2807: /branches/4.3/build-tools/docs/esb https://svn.devel.redhat.com/repos/jboss-soa/branches/4.3/build-tools/docs/esb/ its in there, P12, section 10.2, highlighted in yellow ;-) sorry 10.3 The issue is listed in section 10.3 of the release notes - the confusion was due to its being listed under the Rules JIRA # (RULES-1777). |