Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1149180

Summary: Elastrcsearch mapping for rtgov activities results in spurious events included in call trace
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Gary Brown <gbrown>
Component: RT GovernanceAssignee: Nobody <nobody>
Status: CLOSED UPSTREAM QA Contact: Andrej Vano <avano>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: avano, soa-p-jira
Target Milestone: CR1   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:43:11 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:
Bug Depends On:    
Bug Blocks: 1120384    

Description Gary Brown 2014-10-03 12:39:14 UTC
Description of problem:

When testing a fix for viewing large call traces, generated from a large number of invocations of the 'order1' message, I found that when viewing a call trace for another single transaction (e.g. order3) would include activity events from some of the order1 transactions.


Version-Release number of selected component (if applicable):


How reproducible:

After doing a clean install, with just the quickstarts from ordermgmt folder installed, create a large number of 'order1' transactions using:

mvn exec:java -Dreq=order1 -Dcount=5000

Then create a single order5bad txn.

From the rtgov-ui view the situation associated with the order5bad txn, and see that the call trace includes more than a single red node (representing the failed invocation).

Actual results:

Call trace includes more than one node.

Expected results:

Call trace should only include a single red node.


Additional info:

Comment 7 Red Hat Bugzilla 2025-02-10 03:43:11 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.