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
10 Open 34 Closed
10 Open 34 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

Align ResultMessage#getPayload implementations 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.
#1477 by m1l4n54v1c was closed Sep 23, 2020 Release 4.4.3
@m1l4n54v1c
1
End Saga when Deadline expires 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.
#1469 by m1l4n54v1c was closed Jan 18, 2021 Release 4.5
1
@smcvb
Allow replay on a Saga 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: Feature Use to signal an issue is completely new to the project.
#1458 by m1l4n54v1c was closed Jan 3, 2023 Release 4.7.0
@smcvb
1
Full Concurrency Policy sequence change 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.
#1429 by m1l4n54v1c was closed Jun 12, 2020 Release 4.4
@hsenasilva
2
Aggregate polymorphism 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.
#1216 by m1l4n54v1c was closed Feb 14, 2020 Release 4.3
1
@m1l4n54v1c
Graceful startup/shutdown Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue.
#1215 by m1l4n54v1c was closed Sep 15, 2019 Release 4.3
@smcvb
1
CaughtUp should indicate that all events are handled Status: Obsolete Use to signal this issue is no longer necessary. Type: Bug Use to signal issues that describe a bug within the system.
#1070 by m1l4n54v1c was closed Aug 7, 2019
@abuijze
Unable to stop Tracking EP right after startup 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.
#1066 by m1l4n54v1c was closed Jun 15, 2021 Release 4.5.2
@abuijze @smcvb
1
Spring default processor mode in application.properties 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.
#1064 by m1l4n54v1c was closed Aug 10, 2020 Release 4.2.1
1
InMemoryEventStoreEngine should not store events before the UOW is committed 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.
#1056 by m1l4n54v1c was closed Jan 11, 2021 Release 4.5
1
@smcvb
Dockerize of test scripts Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue.
#1015 by m1l4n54v1c was closed Jun 5, 2019
Streamline AxonServerConnector exception handling 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#885 by m1l4n54v1c was closed Feb 1, 2019 Release 4.1
@abuijze
2
AxonServerConnector doesn't process events after re-connection to AxonServer 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.
#883 by m1l4n54v1c was closed Nov 7, 2018 Release 4.0.1
@m1l4n54v1c
Add possibility to register default TrackingEventProcessorConfiguration 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.
#881 by m1l4n54v1c was closed Feb 21, 2019 Release 4.1
1
@smcvb
1
Rolling back to the safe point in previous segment Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Bug Use to signal issues that describe a bug within the system.
#876 by m1l4n54v1c was closed Nov 2, 2018
1
Streamline QueryBus and QueryGateway error reporting 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#827 by m1l4n54v1c was closed Oct 15, 2018 Release 4.0
@m1l4n54v1c
1
CommandCallback should be removed 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.
#826 by m1l4n54v1c was closed Oct 10, 2018 Release 4.0
@m1l4n54v1c
2
Asserting checked exception while creating an Aggregate 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.
#782 by m1l4n54v1c was closed Jan 4, 2023 Release 4.7.0
@smcvb
4
Saga configuration in Spring 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.
#750 by m1l4n54v1c was closed Sep 10, 2018 Release 3.3.6
@m1l4n54v1c
1
Custom snapshot filtering 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.
#739 by m1l4n54v1c was closed May 24, 2019 Release 4.0
@smcvb
3
Query handlers of the same name and response type within one class 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.
#719 by m1l4n54v1c was closed Apr 14, 2022 Release 4.6.0
1
@CodeDrivenMitch
3
Registering of handler interceptors within EventHandlingConfiguration 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.
#714 by m1l4n54v1c was closed Aug 14, 2018 Release 3.3.5
@m1l4n54v1c
MultiEventHandlerInvoker does not support resetting 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.
#695 by m1l4n54v1c was closed Aug 3, 2018 Release 3.3.3
@m1l4n54v1c
Message serialization/deserialization Status: Obsolete Use to signal this issue is no longer necessary. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#682 by m1l4n54v1c was closed Aug 6, 2019
@abuijze
Expect Scheduled Deadline based on Deadline name 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.
#680 by m1l4n54v1c was closed Jan 9, 2020 Release 4.3
@smcvb
1
ProTip! Type g i on any issue or pull request to go back to the issue listing page.