|
Auto creation of default context not working
|
|
2
|
57
|
July 19, 2024
|
|
Multitenancy feature with Axon in 2024 version
|
|
1
|
66
|
July 16, 2024
|
|
Events are not processed after axon server restart
|
|
2
|
72
|
July 10, 2024
|
|
Connecting to AxonServer node [localhost:8124] failed: UNKNOWN
|
|
9
|
2292
|
July 9, 2024
|
|
Axon Server event store maintenance
|
|
7
|
261
|
July 9, 2024
|
|
Axon server is not starting as h2 file corrupted
|
|
1
|
89
|
July 5, 2024
|
|
Maximum Storage Capacity of Event Store for Enterprise
|
|
2
|
128
|
June 20, 2024
|
|
High availability using Enterprise version of axon server
|
|
12
|
167
|
June 5, 2024
|
|
Axon Server behind AWS load balancer
|
|
8
|
814
|
May 20, 2024
|
|
AxonServer read_aggregate_events sometimes takes seconds to complete
|
|
7
|
127
|
May 10, 2024
|
|
Springbased microservices (using axon framework) not able to access axon server deployed with in same namespace in AWS EKS cluster
|
|
2
|
155
|
April 16, 2024
|
|
Providing wrong config when creating a replication group via the Console leaves the replication group "stuck" and unusable
|
|
3
|
112
|
April 15, 2024
|
|
Events not getting read from different context despite of adding MultiStreamableMessageSource
|
|
1
|
174
|
March 18, 2024
|
|
Currently I'm using mongoDB as my event store. I have 3 different microservices. Is it recommended to use the same collection for event storage of all the 3 microservices ? else different collections is recommended for usage to store events?
|
|
0
|
152
|
March 18, 2024
|
|
I am using Axon Server (SE) and Axon framework (SE) to implement Saga Orchestration. As of now the axon server (SE) saves the .event and .snapshots in flat files
|
|
7
|
304
|
March 12, 2024
|
|
Am new to Axon server. We want to use Axon server for Saga orchestration in distributed microservices in AWS EKS environment
|
|
0
|
159
|
March 5, 2024
|
|
How can I replace the controlDB with postgres or MySQL db in Axonserver open source version. Currently I am deploying the axonserver by running the axonserver.jar. Please let me know
|
|
0
|
129
|
March 5, 2024
|
|
Axon Server is only dispatching queries to the same query handler even though multiple handlers are available
|
|
1
|
208
|
February 15, 2024
|
|
AxonServer SE fails to detect all nodes for transformation
|
|
1
|
194
|
January 31, 2024
|
|
How to find out the segment file, the event is stored in
|
|
0
|
190
|
January 26, 2024
|
|
Unable to connect after upgrade from 4.6.11 to AxonServer 2023.2.x
|
|
6
|
565
|
January 24, 2024
|
|
Replay events automatically
|
|
3
|
386
|
January 16, 2024
|
|
startCompacting fails with "unsupported operation"
|
|
1
|
192
|
January 12, 2024
|
|
Getting xstream dependency exception
|
|
8
|
4713
|
December 21, 2023
|
|
Connection to Axon Server node failed : gRPC status runtime exception : UNKNOWN
|
|
3
|
670
|
December 13, 2023
|
|
Owner of each instance
|
|
1
|
271
|
December 11, 2023
|
|
Choosing a good writing event store database
|
|
1
|
230
|
December 11, 2023
|
|
Axon server mongodb seperated database
|
|
1
|
223
|
November 9, 2023
|
|
Should axon server really "We strongly encourage you to update to the latest Axon Server version, as soon as possible." when I am on the dot-2 release?
|
|
4
|
229
|
November 3, 2023
|
|
Connecting to AxonServer node [localhost:8124] failed: NOT_FOUND: [AXONIQ-1302] default: not found in any replication group
|
|
1
|
1475
|
October 10, 2023
|