How to use tokenstore with JPA on commandside and queryside?

Imported from Google Groups
#1

Hi,

I’m trying to use JPA with TokenStore on the command side in order to test reply events. But my table token_entry is always empty.

I’m using spring-boot and axon 3.3. What kind of configuration do I have to do in order to have it working on the commandside and the query side?

Thanks.

#2

Any help?

#3

I tried to use this:

@Bean
public JpaTokenStore tokenStore(Serializer serializer, EntityManagerProvider entityManagerProvider) {
return new JpaTokenStore(entityManagerProvider, serializer);

}

But I can’t see any message on sprint-boot log and my entry_table always empty.

#4

Any help?

#5

Hi, Here is my configuration for JPA Token Store in Postgres:

@Bean
public TokenStore jdbcTokenStore(DataSource dataSource, Serializer serializer)
        {
    JdbcTokenStore tokenStore = new JdbcTokenStore(
           new SpringDataSourceConnectionProvider(dataSource), serializer);

     tokenStore.createSchema(new PostgresTokenTableFactory());

    return tokenStore;
}

Make sure you have configured correctly your datasource through spring.

#6

Hi,

I tried it but nothing happens. My entry_table is still empty. In log files during the web server start I can’t see any mention to token fetch. Should I put it on command side, right? Any advice?

#7

I suppose you have a database on the query side, and you want to replay events so that the database of your query side gets updated. The tracking processor will do this job, using a token (stored in the tokenStore) , in which token the processor will store its “progress”. All this happens within a context of one service(in your case the query side). What you do in command side, and how you populate your event store etc, is irrelevant to the query side.
The query side service has to have configuration for connection to the event Store, for the tracking processor, and for the token Store.
So in short, you need to have in the query side service, the same configuration you have for the command side service, regarding the event store , plus the configuration for the tokenStore and the tracking processor.

Στις Τετ, 12 Σεπ 2018 - 21:44 ο χρήστης Gustavo Monti <gustavomr@gmail.com> έγραψε:

#8

Hi Vasilis,

Thanks for your awnser. I did what you said but not working yet. :frowning: I started command and query side with differents dbs and on query side I didn’t see any mention to token and my table (token_store) is always empty even I got events.

I’m having trouble to configure postgres as a token store to test replying events.

#9

Well, in that case it would be helpful if you could give us the source code for the query side axon configuration as well as the query side application properties about your event store, the postgres DB and the axon tracking processor.

#10

I attached the files.

Can you see?

application.yml (454 Bytes)

AmqpConfiguration.java (2.92 KB)

#11
  1. you are missing configuration for a tracking processor.
    In the yml file you may specify the existing processor (amqpEvents) as tracking, but I assume you use that for the processing of messages coming from rabbitMq so in that case add another processor like this:

axon:
amqp:
exchange: bank-account.events
eventhandling:
processors:
amqpEvents:
source: complaintEventsMethod
eventsreplay:
mode: tracking

  1. you need a @Component Class annotated with

@ProcessingGroup(“eventsreplay”)

In that class, add this class:

@Configuration
public class ReplayConfiguration {
@Autowired
public void configureProcessors(EventProcessingConfiguration eventProcessingConfiguration) {
eventProcessingConfiguration.registerTrackingEventProcessor(“eventsreplay”);
}
}

And of course, add any Event Handlers you want .

  1. Additional configuration for the Event Store.
    You may missing a few beans in your AmqpConfiguration regarding your event Store. What type of Event Store do you use in your command side?
    You need the exact same configuration for the event Store in the query-side , as you do in the command-side.
    As I have mentioned before, the tracking processor accesses directly the Event Store to get the events from. Not through RabbitMQ but directly. That’s why you have to have configuration for accessing the Event Store, in the service you will place the tracking processor.
#12

I did what you said on itens 1 and 2. No success.

I’m attaching my confi for both (command and query) to see number 3 problems. I’m using in command and query postgres as DB.

If you prefer in order to help me, I can share with you entire project (command and query).

AmqpConfigurationQuery.java (3.03 KB)

AmqpConfigurationCommand.java (4.4 KB)

#13

Yes that maybe helpful. Question: Do you have successfully added events in your event store through the command Side ?

#14

Yes.

I sent to you in private mode my project.

I’ll post here when I got the solution.

Thanks.