You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "YaoHaishi (JIRA)" <ji...@apache.org> on 2018/04/27 06:54:00 UTC
[jira] [Resolved] (SCB-516) AccessLog of EdgeService does not print
traceId
[ https://issues.apache.org/jira/browse/SCB-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
YaoHaishi resolved SCB-516.
---------------------------
Resolution: Fixed
Fix Version/s: java-chassis-1.0.0-m2
> AccessLog of EdgeService does not print traceId
> -----------------------------------------------
>
> Key: SCB-516
> URL: https://issues.apache.org/jira/browse/SCB-516
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
> Reporter: YaoHaishi
> Assignee: YaoHaishi
> Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
> Attachments: ComplieWarning.PNG
>
>
> The access log of EdgeService always prints "-" as traceId.
> It's found out that in TraceIdItem, traceId cannot be gotten, because the dispatcher of EdgeService does not always set invocation into RoutingContext like the VertxRestDispatcher.onRequest() does.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)