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

Aggregate fixture hierarchy behaviour 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.
#2792 by stephan-strate was closed Aug 8, 2023 updated Aug 8, 2023 Release 4.8.1
@smcvb
6
Allow easy configuration of CBOR 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: Feature Use to signal an issue is completely new to the project.
#2776 by CodeDrivenMitch was closed Aug 4, 2023 updated Aug 4, 2023 Release 4.9.0
1
@CodeDrivenMitch
Introduce Maven profile to update versions for non-parent POM related module Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2638 by smcvb was closed Jul 18, 2023 updated Jul 18, 2023 Release 4.8.1
@smcvb
2
Eventual Consistency Question - Doesn't work correctly to get the result of the saga process, from the EventStore using method readEvents Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2782 by ibnNemat was closed Jul 17, 2023 updated Jul 17, 2023
@smcvb
1
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 updated Jul 3, 2023
@smcvb @magnusdurr
5
Subscription Query Update Events are dropped when using AxonServer if the events are created with List.of or stream.toList(). 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
#2768 by heutelbeck was closed Jun 26, 2023 updated Jun 28, 2023
@gklijs @heutelbeck
5
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 updated Jun 27, 2023 Release 4.9.0
@smcvb
1
Set initial token to head when all contained Event Handling Components of a Streaming Event Processor disallow replays Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue. Type: Feature Use to signal an issue is completely new to the project.
#2761 by smcvb was closed Jun 20, 2023 updated Jun 20, 2023
1
JPA storage customization causes an UnknownEntityException: Could not resolve root entity SnapshotEventEntry Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Bug Use to signal issues that describe a bug within the system.
#2725 by barbeque-squared was closed Jun 20, 2023 updated Jun 20, 2023
@smcvb @barbeque-squared
9
Autoconfigure automatic load balancing 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: Feature Use to signal an issue is completely new to the project.
#2453 by CodeDrivenMitch was closed Jun 19, 2023 updated Jun 19, 2023 Release 4.8.0
1
@smcvb
3
DLQ - PSQLException: ERROR: value too long for type character varying(255) 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.
#2752 by oysteing was closed Jun 19, 2023 updated Jun 19, 2023 Release 4.7.6
@smcvb
2
Put test assertion errors on multiple lines 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.
#2755 by barbeque-squared was closed Jun 19, 2023 updated Jun 19, 2023 Release 4.8.0
1
@smcvb
1
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 updated Jun 16, 2023 Release 4.7.6
@smcvb
3
Introduce Polymorphic Aggregate Snapshotting auto-configuration 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: Feature Use to signal an issue is completely new to the project.
#2689 by smcvb was closed Jun 16, 2023 updated Jun 16, 2023 Release 4.8.0
1
@smcvb
JDBC Dead-Letter Queue 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: Feature Use to signal an issue is completely new to the project.
#2350 by smcvb was closed Jun 16, 2023 updated Jun 16, 2023 Release 4.8.0
1
@smcvb
1
Validate test-summary GitHub Action 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: Feature Use to signal an issue is completely new to the project.
#2228 by smcvb was closed Jun 14, 2023 updated Jun 14, 2023 Release 4.8.0
1
@smcvb
Why don't nested unitOfWork go through the cleanup phase ? Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2749 by hrghluug was closed Jun 14, 2023 updated Jun 14, 2023
1
Allow Development mode on test containers Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. 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.
#2461 by CodeDrivenMitch was closed Jun 13, 2023 updated Jun 13, 2023 Release 4.8.0
@smcvb
7
Investigate usage of the Anchore Container Scan in GitHub Actions Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. 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.
#1828 by smcvb was closed Jun 13, 2023 updated Jun 13, 2023 Release 4.8.0
1
@smcvb
2
support for configuring multiple dead letters Queues Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2741 by 2011ashwini was closed Jun 12, 2023 updated Jun 12, 2023
@smcvb
1
Gaps list huge in Tracking Event Processor Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. 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: Question Use to signal the issue is a question of how the project works and thus does not require development
#2728 by Wmaarts was closed Jun 5, 2023 updated Jun 5, 2023
@smcvb @Wmaarts
5
Add db-scheduler implementation of the Event Scheduler and Deadline Manager 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.
#2724 by gklijs was closed Jun 1, 2023 updated Jun 1, 2023 Release 4.8.0
1
@gklijs
Enable tracing in DistributedCommandBus with SpanFactory 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: Feature Use to signal an issue is completely new to the project.
#2403 by smcvb was closed Jun 1, 2023 updated Jun 1, 2023 Release 4.8.0
1
@gklijs
1
use WeakReferenceCache when create a new aggregate throws NullPointerException Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue. Type: Bug Use to signal issues that describe a bug within the system.
#2731 by hrghluug was closed Jun 1, 2023 updated Jun 1, 2023
@hrghluug
2
Add cache using Ehcache 3 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: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
#2420 by smcvb was closed May 25, 2023 updated May 25, 2023 Release 4.8.0
1
@gklijs
1
ProTip! Exclude everything labeled bug with -label:bug.