JMXDetector does not respect the 'timeout'

Description

The JMXDetector does not respect the value of the timeout parameter, and uses the system default for connection timeouts.

This can cause the detector to take several minute to complete a single attempt.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Chandra Gorantla October 3, 2016 at 12:48 PM

PR: https://github.com/OpenNMS/opennms/pull/1050 should resolve this issue

Seth Leger June 8, 2016 at 3:08 PM

Raising to blocker since this could slow down provisioning a lot.

Seth Leger June 3, 2016 at 10:21 PM

Raising priority since this could affect the time it takes to perform provisioning scans.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created April 11, 2016 at 12:21 PM
Updated October 11, 2016 at 11:41 AM
Resolved October 5, 2016 at 6:16 PM