Problem description :
When we execute /v1/regard-application with the below mentioned request body where address of ALT is being updated with dummy address :
request-body :
{
"application-name": "ApplicationLayerTopology",
"release-number": "2.0.1",
"protocol": "HTTP",
"address": {
"domain-name": "ymdhg.j-ir.mdpvb-mr.burx"
},
"port": 3005
}
As there is change in the address, tcp-c LTP of ALT will be updated . As a consequence , update-ltp callback will be sent to ALT .
As the dummy address of ALT is not reachable it is expected that update-ltp callback will return 404 response code . But , response-code is being return as 500 instead of 400.
Note : The issue is being observed for protocol attribute as well.
Problem description :
When we execute /v1/regard-application with the below mentioned request body where address of ALT is being updated with dummy address :
request-body :
As there is change in the address, tcp-c LTP of ALT will be updated . As a consequence , update-ltp callback will be sent to ALT .
As the dummy address of ALT is not reachable it is expected that update-ltp callback will return 404 response code . But , response-code is being return as 500 instead of 400.
Note : The issue is being observed for protocol attribute as well.