This mailing list will be discontinued starting next week, which might have the result that your question will no longer be answered sufficiently over here.
Now, when it comes to your question, you are noticing Axon's requirement to store the progress of handling events in what's called a `TrackingToken`.
These TrackingTokens are stored in the TokenStore, which eventually will end up as a serialized format in the token_entry table.
The processor_name you're spotting there is the default processor name Axon uses if the user didn't specify a processor name.
A sensible default in this case is the package name, as any class would at least have one of those and it follows a reasonable grouping of event handlers under the same package (and thus processor).
If you want to adjust the name, you will either have to define assignment rules in the EventProcessingConfigurer for your Event Handlers or you can use the @ProcessingGroup annotation on your event handling classes.
The latter is typically clearer, as it makes it very effident to your developers in what processing group the event handler he/she is dealing with at that moment belongs to.
Trusting this has clarified things for you Ashwini.
Steven van Beelen
Axon Framework Lead Developer