-
Title
"java.util.concurrent.TimeoutException: Operation timed out after 60000ms" appears in database agent log files -
Description
Timeout error messages for WinRM or WMI queries appear in the database agent log files with the message
"The query ... timed out after 60,000ms and could not be completed, no results will be returned.
java.util.concurrent.TimeoutException: Operation timed out after 60000ms"For example
VERBOSE [Change Tracking_28 []] com.quest.glue.core.remoteconnection.windows.wmi.WMIUtils - The query "select DeviceID, DeviceClass, DeviceName, DriverVersion from Win32_PnPSignedDriver" timed out after 60,000ms and could not be completed, no results will be returned.
java.util.concurrent.TimeoutException: Operation timed out after 60000ms -
Cause
The WMI and WinRM query timeout settings are managed outside of the Agent Status Properties and set to a default of 60 seconds (60000 milliseconds). -
Resolution
Append the following lines to the baseline.jvmargs.config file (%FglAM_HOME%\state\default\config\baseline.jvmargs.config)
Depending on the connection used, there are settings for both for WMI or WinRM
vmparameter.X="-Dwmi.native.connection.timeout.milliseconds=180000";
vmparameter.Y="-Dwinrm.connection.timeout.milliseconds=180000";Where X and Y represent incremental values higher than the other vmparameter entries already in the configuration file.