Symptoms
The EUM Processor does not start and the following error message is listed in the eum-processor.log file.
java.lang.NullPointerException
at com.appdynamics.eum.processor.utils.EUMProcessorHelper.controllerSupportNewEventServiceKey(EUMProcessorHelper.java:360)
at com.appdynamics.eum.processor.utils.EUMProcessorHelper.initializeAccountCredentialStore(EUMProcessorHelper.java:326)
at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:161)
at com.appdynamics.eum.processor.EUMProcessorServerApplication.run(EUMProcessorServerApplication.java:100)
at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:40)
at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:77)
at io.dropwizard.cli.Cli.run(Cli.java:70)
at io.dropwizard.Application.run(Application.java:80)
at com.appdynamics.eumcloud.EUMProcessorServer.main(EUMProcessorServer.java:40)
Diagnosis
Take the output of the accounts and account_credential tables within the eum_db schema of the Controller database.
Example:
./controller.sh login-db
use eum_db;
select * from accounts;
select * from account_credential;
Note: The account name within the accounts table must match that of the account_credential table. The number of records must be the same.
Solution
If the accounts table is purged before provisioning the license, there can be a mismatch in the number of records within the two tables.
To resolve this issue, delete the mismatching account_name row from the account_credential table. Then restart the EUM Processor.
Example:
delete from account_credential where account_name = 'mismatched_account_name';
