You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/10/20 11:30:46 UTC

[jira] Closed: (SLING-705) Set current thread name while handling requests

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

Felix Meschberger closed SLING-705.
-----------------------------------

    Resolution: Fixed

Implemented setting and resetting the thread name in Rev. 706163.

The thread  name is constructed like this:

    127.0.0.1 [1224156108055] GET /system/console/config HTTP/1.1

where the fields have the following meaning:

   1 - IP address of client (or last proxy)
   2 - current system time at start of request processing
   3 - request method
   4 - request URI (path)
   5 - request protocol

> Set current thread name while handling requests
> -----------------------------------------------
>
>                 Key: SLING-705
>                 URL: https://issues.apache.org/jira/browse/SLING-705
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>            Priority: Trivial
>             Fix For: Engine 2.0.4
>
>
> To help in problem determination, it would be usefull to have the SlingMainServlet set the current thread's name to some request information while servicing the request.

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