[SNMP-6] exceptions and timeouts not reported from SNMP walk Created: 14/Jul/15  Updated: 14/Jul/15

Status: In Review
Project: snmp
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Jon Rosenberger Assignee: Jon Rosenberger
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 3997
Priority: Normal

 Description   

AsyncGetHandler can detect and log a timeout or exception but it does not communicate this information back to the caller.

Actual behavior:

Case 1: Timeout (null response PDU from snmp4j)

Log is seen:
ERROR org.opendaylight.snmp.plugin.internal.AsyncGetHandler - Stopped due to timeout; results will be incomplete.

future.get() returns immediately after. Results are incomplete but there is no way for the calling code to know that.

Case 2: An exception thrown anywhere in the handler.

Log is seen with stack trace.

future.get() never returns. Caller will hang indefinitely or until its own timeout.

Desired behavior:

A. Future should be marked done immediately upon error
B. It should be possible to get the exception
C. Timeout should be represented as an exception
D. Incomplete results up to the time of the exception should still be available



 Comments   
Comment by Jon Rosenberger [ 14/Jul/15 ]

remote: New Changes:
remote: https://git.opendaylight.org/gerrit/24126
remote: https://git.opendaylight.org/gerrit/24127

Generated at Wed Feb 07 20:39:11 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.