Following an upgrade of DX NetOps from version 25.4.4 to 25.4.9, users may encounter the following critical symptoms:
The issue is a scale-related side effect of a security hardening fix introduced in the 25.4.9 codebase. A JVM deserialization filter (jdk.serialFilter) implemented for security rejects messages if they contain arrays exceeding a hardcoded limit of 200,000 entries.
Large environments (e.g., those with large Discovery Profiles or high device counts) may trigger this limit, leading to a java.io.InvalidClassException: filter status: REJECTED error in the Data Collector (DC) logs, which interrupts polling and inventory synchronization.
To stabilize the system and restore visibility in the dashboards, perform a global polling reset:
Refer to KB 264417 for the specific steps to stop and start polling across the board.
Alternatively, you can manually increase the maxarray limit in the DC configuration:
/opt/IMDataCollector/scripts.dcmd script.dcmd and locate the APP_OPTS section containing -Djdk.serialFilter.maxarray=200000 to maxarray=1000000.This issue is formally tracked under defect DE209377. Engineering is increasing the default array maximum limit to 1 million entries.
Fixed Version: This fix is scheduled to be included in the DX NetOps 25.4.11 release.