[
https://issues.apache.org/jira/browse/CXF-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691857#comment-16691857
]
John Yin commented on CXF-7254:
-------------------------------
Is this the reason why I do not see
ID: xxxx
in the logged SOAP requests and responses? (I still see the ID: xxxx in logged
REST requests and responses).
Having ID: xxxx in the logged requests/responses is very useful when one has a
large number of similar requests/responses logged at about the same time.
While the ExchangeId can be used to correlate request/response, it is much more
difficult to use than a simple numeric ID. I wish the ID: xxxx can be brought
back. Thanks!
Here is what I see in the log (with CXF 3.2.6 and Springboot 2.0):
2018-11-19 10:03:05.710 [qtp2072830223-53] REQ_IN - REQ_IN
Address: http://...
HttpMethod: POST
Content-Type: text/xml;charset=UTF-8
ExchangeId: 02fe6f42-7dc9-4bdf-adea-4dc86084a108
ServiceName: xxxx
PortName: xxxx
PortTypeName: xxxx
Headers: ...
Payload: ...
> New LoggingFeature Sl4jEventSender does not log the request headers
> -------------------------------------------------------------------
>
> Key: CXF-7254
> URL: https://issues.apache.org/jira/browse/CXF-7254
> Project: CXF
> Issue Type: Bug
> Components: logging
> Reporter: Sergey Beryozkin
> Assignee: Christian Schneider
> Priority: Major
> Fix For: 3.1.11, 3.2.0
>
>
> No request/response properties are reported which, in case of the requests
> with the empty payloads, leads to no info reported at all, while for the
> requests with the payloads only the payload INFO is displayed
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
