[BLOCKER] if called to early, de-serialization seem to produce unpredictable results

[zambrovski]

I triggered the MassOperations for the comparison tests directly out of an @EventListsener reacting on ApplicationStartedEvent.

As a result I got random errors making no sense, regarding impossible values inside of the converted strings... The error disappeared as a soon as I changed the trigger to trigger after 10 seconds (scheduled).

I believe Mr. Heisenberg just entered the room. I believe it is important to understand what prt of the application/framework is causing such problems.

The errors (just for information):

java.lang.NumberFormatException: multiple points
	at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1890) ~[na:na]
	at java.base/jdk.internal.math.FloatingDecimal.parseDouble(FloatingDecimal.java:110) ~[na:na]

java.lang.NumberFormatException: For input string: ""
	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) ~[na:na]
	at java.base/java.lang.Long.parseLong(Long.java:721) ~[na:na]
	at java.base/java.lang.Long.parseLong(Long.java:836) ~[na:na]

and sometimes complete impossible state (can't happen due to business logic check):

org.axonframework.commandhandling.CommandExecutionException: Insufficient Balance: EUR -603, cmd=WithdrawMoney(accountId=f6bddb71-55eb-451f-98f9-c602afaccba0, amount=EUR 10)