MID Server agent log shows "SEVERE *** ERROR *** ClassUtil - class not found"DescriptionYou might notice from the MID Server's agent log the following error message: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: 10/28/21 09:59:21 (546) ECCQueueMonitor.1 SEVERE *** ERROR *** ClassUtil - class not found: Release or EnvironmentAllCauseThe typical "class not found" error message means the MID Server was not able to process the ECC Queue output record. There are other cases where we can see those but we might see the specific class name at the end.In those cases, the suggestion is to search for KB articles or similar cases containing the specific class name. They might have a different Root Cause. This article focuses on the generic error, where there's no class defined at the end.If that's the case, this probably means there are ECC Queue records without important parameters such as Topic and/or Name on it.That's why the MID Server will not be able to handle those and will throw those error messages.ResolutionOut of the box, that would be unexpected behavior.The solution is to find out what is creating those problematic ECC Queue output records.Check the ECC Queue table from the instance (/ecc_queue_list.do) and search by Output records where Topic and Name are empty, for example.If you find them, it probably means an external integration or application is creating them.To solve it, make sure the Output record is created with the correct Topic and Name parameters (RESTProbe, for example, etc).