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
91 Open 1,085 Closed
91 Open 1,085 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

Improve support for a local event store Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#1342 opened Feb 11, 2020 by OLibutzki
6
Usage of Release Candidates Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Feature Use to signal an issue is completely new to the project.
#2589 opened Feb 6, 2023 by OLibutzki
5
Testing command, event and aggregate (de)serialization Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1904 opened Aug 5, 2021 by maartenjanvangool
5
Allow parameterized ResponseType Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1537 opened Oct 13, 2020 by jnfeinstein
5
Contract Testing Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#2990 opened Feb 28, 2024 by meierw
4
Table partitioning for event table Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#2979 opened Feb 14, 2024 by williancolognesitrimble
4
When EmbeddedEventStore enables optimizeEventConsumption (default) it will cause a memory leak of Node sometimes Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Bug Use to signal issues that describe a bug within the system.
#2954 opened Jan 4, 2024 by yitizi
@smcvb @yitizi
4
Allow configuration of a processing group's type through the annotation. Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2788 opened Jul 22, 2023 by vab2048
@vab2048
4
Support for Virtual Threads - JDK21 Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2710 opened May 14, 2023 by mjagus
4
AggregateTestFixture does not validate deadlines set in the past Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2460 opened Oct 27, 2022 by CodeDrivenMitch
4
Return position after Append Events Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Feature Use to signal an issue is completely new to the project.
#1740 opened Mar 22, 2021 by smcvb
4
Logging Suggestion Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1424 opened Apr 28, 2020 by Sam-Kruglov
@smcvb
4
Allow registration of Upcasters on all components that do serialization of messages Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#746 opened Sep 3, 2018 by abuijze
4
Except-Logic for DisallowReplay annotation Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Feature Use to signal an issue is completely new to the project.
#2775 opened Jul 4, 2023 by nils-christian
@CodeDrivenMitch
3
unexpected database load with JpaEventStorageEngine::fetchEvents ramping up Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2641 opened Mar 13, 2023 by junkdog
@junkdog
3
EventProcessingConfigurer should expose registered configurations Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2457 opened Oct 27, 2022 by nils-christian
3
Enable tracing in DisruptorCommandBus with SpanFactory Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Feature Use to signal an issue is completely new to the project.
#2402 opened Sep 27, 2022 by smcvb
3
Add the abilty to fail on unresolved deadline handlers Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2334 opened Aug 19, 2022 by YvonneCeelie
3
Health Indicator for Event Processors Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Feature Use to signal an issue is completely new to the project.
#2138 opened Mar 17, 2022 by smcvb
3
Allow asynchronous code in Sagas Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: On Hold Use to signal that work on this issue is paused. The description should clarify why. Type: Feature Use to signal an issue is completely new to the project.
#1860 opened Jul 2, 2021 by cjdxhjj
3
Distinct Repository beans based on configured Aggregate type Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#1688 opened Jan 22, 2021 by gsteen
3
Interceptor list Spring auto configuration Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#1422 opened Apr 24, 2020 by smcvb
3
Improved API for Aggregate State Transitions Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#1415 opened Apr 21, 2020 by vab2048
3
Support SpEL on an @ProcessingGroup annotation equivalent Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#1266 opened Nov 6, 2019 by jangalinski
3
TestContainer: properties precedence over ServerConnection Type: Bug Use to signal issues that describe a bug within the system.
#3022 opened May 13, 2024 by oleborne
2
ProTip! Follow long discussions with comments:>50.