[IOTDM-51] Put request deletes data Created: 23/Jan/17  Updated: 20/Nov/17  Resolved: 27/Feb/17

Status: Resolved
Project: iotdm
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Miroslav Kovac Assignee: Tomas Janciga
Resolution: Won't Do 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: 7659
Priority: Normal

 Description   

PUT request
Path http://localhost:8181/restconf/config/onem2m-protocol-http:onem2m-protocol-http-providers/HttpProviderDefault

body
{
"onem2m-protocol-http-providers" : [
{
"http-provider-instance-name": "HttpProviderDefault",
"router-plugin-config":

{ "secure-connection": false }

,

"server-config":

{ "secure-connection": false, "server-security-level": "l0", "server-port": 8888 }

,

"notifier-plugin-config":

{ "secure-connection": false }

}
]
}

shouldn`t allow because 8888 is conflict with port for websocket. Although we get a error log in karaf saying "Resources already used for protocol websocket", the response code is 200 or 201 which should be 400 or 500 probably with the message resource already in use. And on top of that it deletes the plugin - in this case http(s)-base. You can test it using this RPC onem2m-plugin-manager-plugin-data that it doesn`t containg http data.



 Comments   
Comment by Tomas Janciga [ 27/Feb/17 ]

The conflicting configuration results with 200 all the times beacuse the init() method of the module is called asynchronously later and if it fails it's just logged and bundle init has failed...
We need to implement some registry of registration failures and provide RPCs to list registration errors and clear registration errors
TODO: Improvement task opened: IOTDM-61 - Implementation of registry of errors and related RPCs for PluginManager

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