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.

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

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

Issues list

Default ReplayToken leads to events not being handled when used with Disallow Replay API Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. 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. Type: Documentation Use to signal issues that describe documentation work.
#2995 by nils-christian was closed Mar 29, 2024 Release 4.9.4
Various issues when importing Axon in Eclipse Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2865 opened Oct 11, 2023 by nils-christian Release 4.10.0
ComponentLocator does not resolve beans from Spring Parent Context 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2855 by nils-christian was closed Oct 19, 2023 Release 4.8.3
TrackingEventProcessor does not start all threads in rare cases Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Obsolete Use to signal this issue is no longer necessary. Type: Bug Use to signal issues that describe a bug within the system.
#2848 by nils-christian was closed Sep 28, 2023
Shutdown-Mechanism of DbSchedulerDeadlineManager 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2844 by nils-christian was closed Oct 2, 2023 Release 4.8.3
AxonDbSchedulerAutoConfiguration can not be used multiple times in hierarchical Spring context due to static fields 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2843 by nils-christian was closed Oct 2, 2023 Release 4.9.0
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
Improve JavaDoc of the CommandTargetResolver 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2742 by nils-christian was closed Jun 27, 2023 Release 4.9.0
Deprecated fallback warning with Spring 6.0.5 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.
#2630 by nils-christian was closed Mar 9, 2023 Release 4.7.3
HandlerDefinitions and HandlerEnhancerDefinitions are shared between multiple Spring Application Contexts 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.
#2590 opened Feb 6, 2023 by nils-christian
Axon Spring AutoConfiguration binds wrong EventStore (Jakarta/Javax) Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. 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.
#2584 by nils-christian was closed Feb 1, 2023 Release 4.7.1
Upcasters are not applied to DeadLetterQueue entries 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.
#2500 opened Nov 23, 2022 by nils-christian
DeadLetterQueue uses wrong Serializer to (de)serialize Tokens Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. 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.
#2485 by nils-christian was closed Nov 15, 2022 Release 4.6.3
NullPointerException on Shutdown without Start 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.
#2481 by nils-christian was closed Dec 2, 2022 Release 4.6.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
JpaSagaStore cannot be used without XStream Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. 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.
#2431 by nils-christian was closed Oct 11, 2022 Release 4.6.2
Documentation regarding Spring Boot AutoConfiguration for Dead-Letter Processors does not work Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. 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. Type: Incorrect Repository Use to signal the issue is constructed in the wrong repository.
#2394 by nils-christian was closed Nov 8, 2022 Release 4.6.0
Add ConditionalOnBean to InfraConfiguration Beans Ideal for Contribution 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2383 by nils-christian was closed Dec 21, 2022 Release 4.7.0
Events are not processed when optimize-event-consumption is disabled Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. 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.
#2382 by nils-christian was closed Sep 29, 2022 Release 4.6.1
Event storage engines cannot be used without XStream Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. 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.
#2364 by nils-christian was closed Sep 19, 2022 Release 4.6.1
Using deadlines with DefaultConfigurer leads to NPE Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. 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.
#2317 by nils-christian was closed Aug 10, 2022 Release 4.6.0
Replaying subscribing event processors Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Feature Use to signal an issue is completely new to the project.
#2304 by nils-christian was closed Aug 9, 2022
TrackingEventProcessor cannot be reset immediately after shutdown in very rare cases 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.
#2293 by nils-christian was closed Aug 1, 2022 Release 4.5.15
TrackingEventProcessor does not wait for his worker threads to shut down Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2290 by nils-christian was closed Jul 20, 2022 Release 4.5.15
Incorrect warning message in case of shutdown timeout Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. 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.
#2289 by nils-christian was closed Jul 19, 2022 Release 4.5.15
ProTip! Find all open issues with in progress development work with linked:pr.