Bug 595792
Summary: | Have agent-server comm start earlier | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Heiko W. Rupp <hrupp> |
Component: | Communications Subsystem | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED WONTFIX | QA Contact: | Corey Welton <cwelton> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.0.0 | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-03-24 13:24:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Heiko W. Rupp
2010-05-25 15:57:45 UTC
mazz - what do you think of the suggestion? This would require a reshuffling of the startup routines in StartupServlet. In past experience, changing the ordering of when the comm layer starts is VERY dangerous and can have many side effects. Several times in the past we tried changing the ordering of the StartupServlet and its come back to bite us because of the side effects that we didn't realize would happen. Therefore, unless absolutely necessary, we should not be changing when the comm layer starts up (or any of the ordering of things in StartupServlet). If the only problem here is an exception message in the logs, that does not rise to the level to where we should change this. will not be shuffling the startup routines in StartupServlet. Alot has gone into getting the StartupServlet "just right" and agent-server comm is getting started in the proper place. If we move it up earlier, other bad things will happen. See the comments in StartupServlet for more info on why we should not adjust this stuff unless absolutely necessary (and even in that case, it still may not be possible to re-shuffle the startup code without introducing other bugs). |