Bug 1020953
Summary: | JTS qa test CrashRecovery12_Test03 fails running with HornetQ object store | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ondrej Chaloupka <ochaloup> |
Component: | Transaction Manager | Assignee: | Michael <mmusgrov> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondrej Chaloupka <ochaloup> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0, 6.2.4 | CC: | tom.jenkinson |
Target Milestone: | GA | ||
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-19 12:42:45 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: |
Description
Ondrej Chaloupka
2013-10-18 15:15:38 UTC
Note that this failure is a bug in the test design itself and does not affect the functionality of narayana itself - my fix is to the test suite and I did not touch the code that goes into the product Gytis Trikleris <gytis> updated the status of jira JBTM-1980 to Closed Gytis Trikleris <gytis> updated the status of jira JBTM-1980 to Reopened Gytis Trikleris <gytis> made a comment on jira JBTM-1980 Looks like the same issue http://172.17.131.2/view/Narayana+BlackTie/job/narayana-hqstore-jacorb/22/TESTS=QA_JTS_JACORB,jdk=jdk7.latest,label=linux/ Michael Musgrove <mmusgrov> updated the status of jira JBTM-1980 to Resolved Michael Musgrove <mmusgrov> made a comment on jira JBTM-1980 The referenced CI failure on the previous comment affects 5.0.0.CR1 only so I am resolving the JIRA again since the problem is fixed on the 4.17 branch. I have removed 5.0.0.CR1 from the fix for field. See linked JIRA to track the problem on the 5.0.0.CR1 branch) Michael Musgrove <mmusgrov> updated the status of jira JBTM-1980 to Reopened Michael Musgrove <mmusgrov> made a comment on jira JBTM-1980 The fix is in both branches (4.17 and master) so even though the failure was seen against master it could occur in 4.17 also. From the logs it looks like the test task is being reaped after 58 seconds (although the test config says it should only be reaped afater 240 seconds). This means that my fix to overcome port recycling did not have sufficient time to take effect. My line of investigation is to determine why the task was reaped early. Michael Musgrove <mmusgrov> updated the status of jira JBTM-1980 to Resolved Michael Musgrove <mmusgrov> made a comment on jira JBTM-1980 I am unable to reproduce this issue - the PR adds extra logging information to help diagnose if it does ruccur. Michael Musgrove <mmusgrov> updated the status of jira JBTM-1980 to Reopened Michael Musgrove <mmusgrov> made a comment on jira JBTM-1980 Recurrence of the same issue (with extra trace) Michael Musgrove <mmusgrov> made a comment on jira JBTM-1980 The task that checks for recovery runs before the task that generates the crash scenario has finished. I have added a fix that delays the second task until the first task is ready. I'm testing it with a dedicated job: http://172.17.131.2/job/JBTM-1980-hqstore/ to test my fix Michael Musgrove <mmusgrov> updated the status of jira JBTM-1980 to Resolved Michael Musgrove <mmusgrov> made a comment on jira JBTM-1980 The latest failure is because the client task that creates the crash record takes a while to start (because of port recycling) and the checker task that validates recovery occurred runs before the client has had time to generate the crash rec. The fix is to wait for the client task to become ready before launching the checker task. I have only applied the fix to CrashRecovery12_Test03. If we ever get similar failures for other tests then we should apply the same fix as necessary. Tom Jenkinson <tom.jenkinson> updated the status of jira JBTM-1980 to Closed Can we close this one yet or are you still seeing the failure? Hi, I can't see the problem for 4.17.21.Final which is under 6.3.0.GA. So setting as verified from QA point of view. Thanks Ondra |