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.

Sign up for GitHub

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

Jump to bottom

TracingAutoConfiguration should not be auto-configured after InfraConfiguration #105

Closed
lfgcampos opened this issue Dec 20, 2020 · 0 comments · Fixed by #106
Closed

TracingAutoConfiguration should not be auto-configured after InfraConfiguration #105

lfgcampos opened this issue Dec 20, 2020 · 0 comments · Fixed by #106
Assignees
@lfgcampos
Labels
Priority 1: Must Status: Resolved Type: Bug
Milestone
Release 4.5

Comments

@lfgcampos
Copy link
Contributor

Basic information

  • Axon Framework version: 4.4.x
  • JDK version: any
  • Tracing Extension version: 4.4
  • Complete executable reproducer if available (e.g. GitHub Repo): look here

Steps to reproduce

It is similar to the linked issue on extension-kafka and was also noticed by our users on our discuss.

Expected behaviour

TracingCommandGateway and TracingQueryGateway should be used.

Actual behaviour

Default command and query gateway is always used, because AxonAutoConfiguration goes first, and defaultCommandGateway is created there. So tracingCommandGateway in TracingAutoConfiguration is ignored.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lfgcampos lfgcampos

Labels
Priority 1: Must Status: Resolved Type: Bug
Projects
None yet
Milestone
Release 4.5
Development

Successfully merging a pull request may close this issue.

AutoConfiguration should happen before Framework InfraConfiguration AxonFramework/extension-tracing
2 participants
@smcvb @lfgcampos