Bug 1301103
Summary: | goferd taking 100% CPU after successful reconnect to qdrouterd after a longer time | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> |
Component: | Foreman Proxy | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.1.5 | CC: | adahms, ahuchcha, bkearney, cdonnell, chrobert, cwelton, ddevra, gabicr, hasingh, hklein, jentrena, katello-bugs, katello-qa-list, kgiusti, kshravag, mcressma, mmccune, mshimura, nmiao, peter.vreman, pierre-yves.goubet, pmoravec, rmahique, sghai, smeyer, sreber, wharris, xdmoon |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the Qpid proton reactor class did not abort internal pipes correctly when a connection was reset. During reconnect, the reactor thread occasionally entered an infinite loop, causing high CPU consumption. The internal pipes are now properly closed and the high CPU consumption no longer occurs on reconnect.
|
Story Points: | --- |
Clone Of: | 1295957 | Environment: | |
Last Closed: | 2016-01-28 07:25:41 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: | 1295957 | ||
Bug Blocks: | 1122832 |
Comment 2
Sachin Ghai
2016-01-27 10:11:31 UTC
Moving this bz to verified as per comment2. The other clients (rhel6, rhel5.11) tests can be covered in other bz 1295957 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:0076 |