[jira] Resolved: (SLING-1872) Web Console Request Log display unusable under load

["Felix Meschberger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-1872.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: Engine 2.1.2

Rev. 1037739: Revamp the recent requests display:
  - Adapt to new JQuery UI styles
  - Use POST requests to clear recordings
  - Add configuration option to SlingMainServlet for max number of recorded requests
  - Replace rotated array by LinkedHashMap to keep requests
  - Copy displayed values instead of keep the SlingHttpServletRequest for display

> Web Console Request Log display unusable under load
> ---------------------------------------------------
>
>                 Key: SLING-1872
>                 URL: https://issues.apache.org/jira/browse/SLING-1872
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.1.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: Engine 2.1.2
>
>
> The Web Console plugin to list the recent requests processed by Sling does not properly work.
> This plugin internally uses a rotating buffer of recent requests and displays information about these buffer entries. Access to a single entry then takes place with the numeric index into this buffer. This of course fails under load when the rotating buffer is constantly being overwritten.
> We should devise another mechanism to show information on requests. One option would be an LRU Cache, which is indexed by some unique key, which is never reused (may well be a steadily growing number, of course). Requests then happen by using the key.
> Under load the plugin can then either cope by allowing a bigger cache size (e.g. temporarily increasing the size) but at least handle the case of a request having fallen off the cache more gracefully.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.