You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/09/20 05:59:20 UTC

[jira] [Commented] (FELIX-4615) Re-enable ability to activate Jetty logging through HTTP service properties

    [ https://issues.apache.org/jira/browse/FELIX-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505697#comment-15505697 ] 

Carsten Ziegeler commented on FELIX-4615:
-----------------------------------------

[~walkerr] Is this still relevant? I cant find the property "org.apache.felix.http.debug" in the current code base at all

> Re-enable ability to activate Jetty logging through HTTP service properties
> ---------------------------------------------------------------------------
>
>                 Key: FELIX-4615
>                 URL: https://issues.apache.org/jira/browse/FELIX-4615
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>            Reporter: Rob Walker
>            Priority: Minor
>
> In older HTTP Service versions, Jetty's own internal logging could be enabled either through direct control of Jetty properties, or via HTTP Service properties. It looks like in recent versions this ability has been lost.
> The following debug flag does enable tracing of the service code itself:
> org.apache.felix.http.debug = true
> But this flag does not wire in a Logger for Jetty messages, or set it's level to debug.
> It's possible that two flags/config approaches may be needed to allow fine grained control: one for controlling service debug messages (as at present); and an additional one to enable Jetty debug messages



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)