Running Requests give you the ability to view and administer running requests on your server. From the FusionReactor Administrator, click "Running Requests" from the table of contents (Requests section) and you will see the Running Requests screen.
At the top of the screen you will see the refresh bar. You can use this to manually or automatically update the running requests listed below. For each request shown you will see the time at which it began, the IP address of the machine which created it, the page which was actually requested, the amount of time it has been running and the state of the memory when this request entered the system. Above the running requests you will also see the state of the memory right now.
The request table has the following columns:
Started |
The time at which the request was received. |
IP |
The IP address of the caller. |
ID |
The request ID and the name of the thread which is servicing the request. |
URL/Parameters |
The URL path and parameters passed to the request. You can turn on or off the hostname in the URL by modifying the URL Format value on the Request Settings page. |
Time (ms) |
The number of milliseconds that the request has been running so far. |
Memory (KB) |
A snapshot of the state of system memory at the time the request was started. The following values are shown:Used memory as a percentage of the total available to the JVM, the actual used memory value in KB, and the margin of free memory available before the JVM must extend its own heap (if it has not already reached its limit). |
The Running Requests page lists all currently running pages as well as showing the current memory values.
Max |
The amount of memory available to the JVM (this is a hard upper limit). |
Alloc |
The amount of memory currently allocated by the JVM for its heap – this may grow until the ‘Max’ value is reached |
Free |
The amount of free memory from the currently-allocated heap |
Used |
The amount of memory which is actually in use. This is expressed as a percentage as well as in KB. |
If there are requests queued due to Crash Protection then they will be listed below the currently running requests. The queued requests are listed in the same format as the running requests (see above) but there is an extra column giving you the reason that the request was queued.
You can change the order in which requests are displayed on this page by clicking on any of the column titles. Clicking on a title for a second time will reverse the order on that column.
Each request listed on this page has four icons next to it. They are:
Stack Trace |
Clicking this button will take you to the Stack Trace page, allowing you to see the current Java stack trace of the request. |
Request Detail |
Clicking this button will take you to the Request Details page, allowing you to access all information associated with a request; e.g cookies, JDBC, headers and User Trace Markers. |
Kill Request |
Clicking this button allows you to manually kill any tracked request. You will be asked if you are sure. Click on OK to kill the request.
WARNING: Although FusionReactor first attempts to signal the requestto let it exit safely, if this times out or you skip the timeout, then the request will be killed in a very abrupt manner. Please be aware that in some very limited cases, this can cause the JVM to become unstable. |
Add to CP Restrictions |
If you click this button then you will be taken to the Crash Protection Restrictions page which will be filled out for this request. |
As well as the icons, you can also Stack Trace or Kill All currently running requests by using the two buttons ("Stack Trace ALL" and "Kill ALL") above the request list.
WARNING: The "Kill ALL" button does not give the requests time to complete in their own time. Using this feature can cause the JVM to become unstable.
At the top of the page you will see the standard page header. At any time you can click the refresh button to update the main content. Alternatively you can select a time period from the drop-down box to update the content automatically. Selecting "None" from the drop-down box will stop the automatic refresh.