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

ASF subversion and git services commented on SOLR-18042:
--------------------------------------------------------

Commit a8c8f6270f53ae1454624814c48c8e5533d21be5 in solr's branch 
refs/heads/branch_10x from Gus Heck
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a8c8f6270f5 ]

SOLR-18042 Manage MDC Logging Context setup/teardown in a servlet filter. 
(#3985) (#3996)



> Manage MDC logging context in a Filter
> --------------------------------------
>
>                 Key: SOLR-18042
>                 URL: https://issues.apache.org/jira/browse/SOLR-18042
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Server
>    Affects Versions: main(11.0)
>            Reporter: Gus Heck
>            Assignee: Gus Heck
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Another thing we do that is meant to be managed on a per-request basis is set 
> up and tear down of the MDC logging context. This is slightly less trivial 
> than exclusions, because it will introduce a second filter that "knows about" 
> core container, but enabling such a thing is exactly why I previously moved 
> the startup of CoreContainer to a ServletListener (and thus it should exist 
> before all Filters are configured). If that move was truly copacetic, then 
> this should be trivial, but of course the proof is in the pudding.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to