You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/01/29 11:25:13 UTC

[jira] [Updated] (SLING-2717) SlingMainServlet: changing config without providing a path pattern disables requests recording

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

Bertrand Delacretaz updated SLING-2717:
---------------------------------------

    Description: After saving the SlingMainServlet config from /system/console/configMgr, leaving the "Recorded Request Path Patterns" parameter empty, the plugin at /system/console/requests always says "recorded 0 requests" and does not show any new requests.  (was: After changing that value from /system/console/configMgr, the plugin at /system/console/requests always says "recorded 0 requests" and does not show any new requests.)
        Summary: SlingMainServlet: changing config without providing a path pattern disables requests recording  (was: Changing "number of requests to record" in SlingMainServlet config disables recording)
    
> SlingMainServlet: changing config without providing a path pattern disables requests recording
> ----------------------------------------------------------------------------------------------
>
>                 Key: SLING-2717
>                 URL: https://issues.apache.org/jira/browse/SLING-2717
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.2.6
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: Engine 2.2.8
>
>
> After saving the SlingMainServlet config from /system/console/configMgr, leaving the "Recorded Request Path Patterns" parameter empty, the plugin at /system/console/requests always says "recorded 0 requests" and does not show any new requests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira