| Summary: | Call time widget fails with 'null' | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Alan Santos <asantos> | ||||
| Component: | RT Governance | Assignee: | Thomas Hauser <thauser> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Pechanec <jpechane> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.0 GA | CC: | asantos, atangrin, eric.wittmann, kconner, kejohnso, soa-p-jira | ||||
| Target Milestone: | ER7 | ||||||
| Target Release: | 6.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Alan Santos
2013-11-17 17:55:52 UTC
Hi Alan Can you describe the steps to reproduce these problems from a clean start (i.e. install). Regards Gary Created attachment 825699 [details]
sample h2 database which can be used to reproduce the exception
This issue is being caused by a large json response (177kb). The service has the response incorrectly marked as producing "image/svg+xml" - wondered if this was the problem, but the exceptions occur even if changed to "application/json". Will assign to Eric to see whether this could be a gadget server issue, as the exception stack indicates the client is closing the connection. Shindig (the gadget api framework we use) had a default http connection timeout for REST calls of 5s and an http connection read timeout of 5s. So this was presumably hitting the 5s mark and then failing. I have fixed this by making these two timeouts configurable via gadget-server.properties. The properties that drive this behavior are: gadget-server.config.auth.connection-timeout=10000 gadget-server.config.auth.read-timeout=60000 These properties are now required to be in gadget-server.properties - there are no defaults. The values are in milliseconds, so the above uses a 10s connection timeout and a 60s read timeout. These seem like reasonable values. I'm going to assign this to thauser in case there are installer implications. As long as these changes are present in the gadget-server.properties file at build time, there should be no installer changes required for this issue. *** Bug 1032008 has been marked as a duplicate of this bug. *** Verified in ER7 that increasing timeout mitigates the issue |