Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

async call not work when use zipkin #3576

Closed
maxiaoguang64 opened this issue Feb 28, 2019 · 5 comments
Closed

async call not work when use zipkin #3576

maxiaoguang64 opened this issue Feb 28, 2019 · 5 comments
Assignees

Comments

@maxiaoguang64
Copy link
Contributor

dubbo version 2.6.x
zipkin plugin version 5.6.1

y1 r08 0hw fm c py 4kj

result.hasException() will call future.get() to wait result

@beiwei30 beiwei30 assigned qinliujie and chickenlj and unassigned qinliujie Mar 1, 2019
@maxiaoguang64
Copy link
Contributor Author

@chickenlj can we disscus this

@chickenlj
Copy link
Contributor

result.hasException() will call future.get() to wait result

Sorry, but I don't understand why result.hasException will trigger future.get().

Can you provide the complete code implementation which the above snippet belongs to?

@maxiaoguang64
Copy link
Contributor Author

@chickenlj
i am sorry, i use dubbo 2.7.0-SNAPSHOT.
image
but 2.7.0-RELEASE already fix it.
image

image
Is this necessary?
oneway and async are difference.
image
image
call tracing consumer--->provider1--->provider2
use async call
but i can't wait result.

@maxiaoguang64
Copy link
Contributor Author

@chickenlj can i do something?

@chickenlj
Copy link
Contributor

but 2.7.0-RELEASE already fix it.

Yes, the bug you reported will be fixed in 2.7.1 release.

img

Is this necessary?

You can use RpcContext.getCompletableFuture() and add callback to CompletableFuture directly.
And I would recommend you record the Finish Span in Filter.onResponse, it works for both sync and async scenario, you do not need to register any callback. Whenever onResponse is called, indicates the actual result returns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants