Data Collector appears to hang or crashes in r2.7 Early Access/GA (build 133). Or devices could be missing polled data. This is due to too many threads and/or ports being created to service MVEL SNMP calls. This excessive consumption of resources can manifest in loss of polled data for some or all devices.
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)[:1.8.0_60]
SELECT d.hostname, v6_ntoa(d.primary_ip_address) as "address", i.item_id
FROM item i
JOIN v_item_facet vi ON i.item_id = vi.item_id
JOIN poll_item pi ON i.item_id = pi.item_id
JOIN device d ON pi.device_item_id = d.item_id
WHERE vi.facet_qname LIKE '%CiscoQosClassMap%';
This condition is only seen if there is a device actively being polled using advanced MVEL expressions that perform additional snmpgets / snmpbulkgets in variables or expressions. Out-of-box, there are two Qos class map certifications that use such expressions. Customers should confirm that they either have devices being polled using the QoS vendor certifications, or identify that they have some custom certification or extension that uses such expressions. See the “Symptoms” section noted above to determine if you are affected by this condition.
Temporary workaround (prior to upgrading the Data Collector)
An updated DC installer is being provided on the download portal for the CA PM r2.7 product. This installer MUST be used to upgrade all Data Collectors when installing r2.7 to prevent any data loss.
The fix will also be available in the first monthly update kit for r2.7.