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

Wrapping call to initial fetchSegments in transaction. #1908

Merged
merged 2 commits into from
Aug 12, 2021
Merged

Wrapping call to initial fetchSegments in transaction. #1908

merged 2 commits into from
Aug 12, 2021

Conversation

brunchey
Copy link
Contributor

No description provided.

@CLAassistant
Copy link

CLAassistant commented Aug 11, 2021

CLA assistant check
All committers have signed the CLA.

@smcvb smcvb added Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: In Progress Use to signal this issue is actively worked on. Type: Bug Use to signal issues that describe a bug within the system. labels Aug 11, 2021
@smcvb smcvb added this to the Release 4.5.4 milestone Aug 11, 2021
Copy link
Member

@smcvb smcvb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testing this change is gonna be tough... The only thing I can think of right now is spying the TransactionManager and verifying it is used. The problem is that this piece of code is tucked away in a separate thread with its own idea on time... So, would you mind testing this out with the sample project you were talking about that failed due to this missing transaction wrapping?

@brunchey
Copy link
Contributor Author

I have tested this locally with the micronaut application I am developing and this resolved the issue

@brunchey brunchey merged commit 8ad06b4 into AxonFramework:axon-4.5.x Aug 12, 2021
@smcvb smcvb added Status: Resolved Use to signal that work on this issue is done. and removed Status: In Progress Use to signal this issue is actively worked on. labels Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants