[jira] [Commented] (SCB-516) AccessLog of EdgeService does not print traceId

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SCB-516:
------------------------------------

coveralls commented on issue #671: [SCB-516] fix accessLog traceId printing 
problem in EdgeService
URL: 
https://github.com/apache/incubator-servicecomb-java-chassis/pull/671#issuecomment-383468848
 
 
   
   [![Coverage 
Status](https://coveralls.io/builds/16643775/badge)](https://coveralls.io/builds/16643775)
   
   Coverage increased (+0.01%) to 87.372% when pulling 
**cdbe454914365e6ec334f409a07b744077f8099e on 
yhs0092:fix_EdgeService_accessLog_print_traceId_problem** into 
**3b05f0616b34aa10651d7d4730218f1831cd40e9 on apache:master**.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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
>         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)