We have a Omada 3.x Controller ruinning and supporting mostly old EAP115 V1/V2 and EAP110-outdoor V1 APs. These AP models are not supported by the new Omada 5.x controller and therefore in order to continue using old controller in a Rocky Linux 9.2 VM on Windows PC. We noticed that every 10s or so, their is an Null pointer exception that is being shown and is in the file /opt/tplink/EAPController/logs. The startup log file is free from errors. Here are the Logs seen:



Any Idea what this means and how to resolve this ? The controller ios otherwise tables but few 1-2 APs out of 10 on the cxontroller randomly restart every day. Here is the information about the VM: