Bug 1032008

Summary:	executing 5k orders causes call trace widget to stop working
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Alan Santos <asantos>
Component:	RT Governance	Assignee:	Gary Brown <gbrown>
Status:	CLOSED DUPLICATE	QA Contact:	Jiri Sedlacek <jsedlace>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	atangrin, kejohnso, oskutka, soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1032006	Environment:
Last Closed:	2013-11-20 13:12:20 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 Alan Santos 2013-11-19 11:13:43 UTC

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

How reproducible:
every time

Steps to Reproduce:
1. deploy ordermgmt-app
2. deploy ordermgt-ip
3. do not open gadget server
4. execute mvn exec:java -Dreq=order1 -Dcount=5000
5. open gadget server, add value='1' to call tracce widget

Actual results:
widget is not updated, there are no errors in log.


Expected results:
widget is updated w/5k instances (or some reasonable subset)

Comment 3 Gary Brown 2013-11-20 13:12:20 UTC

In 1031413, the call trace is much larger, so the client timeout occurs while it is still being produced, and therefore causes the exception in the server.

The increased timeout should fix this issue.

*** This bug has been marked as a duplicate of bug 1031413 ***