Skip to content

Issues: AxonFramework/AxonFramework

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

Clear current search query, filters, and sorts
0 Open 4 Closed
0 Open 4 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Behavioral change in 4.9 JpaEventStoreAutoConfiguration Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. 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.
#2900 by magnusdurr was closed Nov 16, 2023 Release 4.9.1
@smcvb @magnusdurr
5
Gaps in the GapAwareTackingTokens are not cleaned up in the TokeStore after the specified gapTimeout. Status: Resolved Use to signal that work on this issue is done. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2771 by magnusdurr was closed Jun 30, 2023
@smcvb @magnusdurr
5
Duplicate initialization of TrackingEventProcessor worker threads 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.
#2751 by magnusdurr was closed Jun 16, 2023 Release 4.7.6
@smcvb
3
Same event received twice in tracking event processor after database connectivity glitch Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Obsolete Use to signal this issue is no longer necessary. Type: Bug Use to signal issues that describe a bug within the system.
#2232 by magnusdurr was closed Oct 3, 2022
@abuijze @smcvb
8
ProTip! no:milestone will show everything without a milestone.