Title:
Bug 86142:(Watson Migration Closure)There seems to be a mistake in the Server Manager details view display of information
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/LowImpact
Reporter/Name(from Bugbase): Charlie Arehart / charlie arehart (Charlie Arehart)
Created: 02/02/2011
Components: Server Monitoring
Versions: 9.0.1
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Most users will encounter
Locale/System: English / Platforms All
Vote Count: 1
Problem:
There seems to be a mistake in the Server Manager details view display of information. What is "Active Requests" supposed to be, compared to "Running Requests"? It always is showing the same data as Running Requests in my observations. Indeed, Looking at the results of the underlying getheartbeat method of the servermanager.cfc, there's no equivalent to anything called "active requests". In fact, I'm willing to bet that the Active Requests is for some reason mistakenly pointing to the value for Running requests. Here's how I would assert that. I just filed a bug (86141), showing that on Standard deployments of CF, all 3 of these request-related fields show "no data", and I pointed out that in the getheartbeat result, it's only the REQQUEUED and REQRUNNING that have the mistake of coming back as strings rather than numbers. It seems then that since "active requests" also shows "no data" on Standard deployments, and shows the same data as "running requests" on Enterprise/Developer ones, it 's likely looking at reqrunning by mistake. I don't see any other field in the getheartbeat result that is not displayed on screen.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3043272
External Customer Info:
External Company:
External Customer Name: charlie arehart
External Customer Email: 03D0090C44723473992015D5
External Test Config: 02/02/2011Attachments:
Comments: