When a MID server has a property record [ecc_agent_property] specific to that MID server, as well as another property record with same name (but with different value) global to all MID servers , the MID server can sometimes incorrectly use the global record instead of the specific record.
Which of the two record gets used can't be predicted. It probably depends on the underlying unsorted record order of the database which users have no control over.
Don't know a reliable way to reproduce since behavior is non-deterministic.
It has been seen for mid.sm.discolog.max_object_size, where the out-of-box global record with value 1000 is used instead of a MID Server-specific record, and the Discovery Pattern log still says the value is 1000:
The max object size reached the maximum limit of . To adjust this use the mid property mid.sm.discolog.max_object_size.
It has also been seen with mid.sa.ssh.timeout when trying to increse it to help with an Oracle DB pattern discovery.
This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.
If you need a MID-specific property, then delete the global property, and create MID specific property for each MID server.
If Specific MID field is empty, then its treated as global property.