Quick comment... StatisticsManager.statsRequestSender is
sending requests to all Nodes to known to the system... but it should only send messages to all known FlowCapableNodes... not all Nodes are FlowCapable Nodes 
Hi Jan,
I fixed this issue and pushed code changes through
http://git.opendaylight.org/gerrit/4356
Can you please test it once and confirm that it fixes the issue.
Will close this bug afterward.
Thanks
Anil
This is now blocking Netconf testing. Requesting the entire operational data tree from a large netconf node (e.g. xr) can take a long time.
Hi Jan,
I already fixed this issue and the code changes are already merged to code base. I changed the code so that it only sends stats request to FlowCapableNode only.
Do you still see this issue with latest code base?
If yes, then there can be two possible reason:
1) Either netconf devices are FlowCapableNode, is it the case ??
2) or getAugmentation has some bug, and its passing following condition
if(targetNode.getAugmentation(FlowCapableNode.class) != null)
Thanks
Anil
I just submitted fix for this issue, it's on https://git.opendaylight.org/gerrit/#/c/4764/ I added support for hexadecimal, octal and decimal numerical systems as are stated in RFC 6020.
There are still rules that users have to follow:
An integer value is lexically represented as an optional sign ("+" or "-"), followed by a sequence of decimal digits.
The hexadecimal notation consists of an optional sign ("+" or "-"), the characters "0x" followed a number of hexadecimal digits, where letters may be uppercase or lowercase.
The octal notation consists of an optional sign ("+" or "-"), the character "0" followed a number of octal digits.
More on http://tools.ietf.org/search/rfc6020#section-9.2.1
Although the yang specification clearly states that: "In the XML instance documents, an integer is always interpreted as a decimal number, and leading zeros are allowed." Thus in general users SHOULD use decimal numbers in xml instances.