[NETCONF-467] Restconf often invokes RPCs with null payload Created: 08/Sep/17  Updated: 15/Mar/19  Resolved: 13/Oct/17

Status: Resolved
Project: netconf
Component/s: restconf-nb
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Martin Dindoffer Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File restconf_payload.pcapng    
Issue Links:
Duplicate
duplicates NETCONF-452 NPE when adding routes to app-peer Resolved
External issue ID: 9125

 Description   

====Summary====
Title says it all - Restconf often calls RPC implementations with null payload.

====Examples====
One example of this is in SXP csit https://logs.opendaylight.org/releng/jenkins092/sxp-csit-1node-basic-all-nitrogen/125/
However I can easily reproduce this when running SXP basic robot tests on my local machine.

====Symptoms====

  • Wireshark verified Robot sends valid requests with xml payload. (see attachment)
  • Walking back through stackframes I saw that AbstractResourceMethodDispatchProvider (line 185) in jersey already holds params with null data
  • However, http headers are parsed correctly

====Enviro====
Affects both Nitrogen and Oxygen.

 Comments   
Comment by Martin Dindoffer [ 08/Sep/17 ]

Attachment restconf_payload.pcapng has been added with description: RPC request parsed as null

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