Error handling: Empty response generated by NCP-B Client Connector
We’ve faced following issue with Italy (NCP-A):
PL’s NCP-B (Client Connector) asks for a prescription list of IT’s NCP-A.
IT’s NCP-A National Connector answers with ‘null’, IT’s server interprets null as “eP registry not accessible error and sends back an response with code 4103 and severity “warning”.
We’ve debugged this situation in our internal environment (prepared mocked NCP-A to send back null in this situation)
PL’s NCP-B (Client Connector) ignores 4103 code, and answers back to the National Infrastructure with empty response:
{code:java} 2023-04-06T16:48:37.097+02:00 https-openssl-nio-8443-exec-5 DEBUG LOGGER_CLINICAL.logSoapMessage(296) - Outgoing 'queryDocuments' response message to portal:
<soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope> soapenv:Header/ soapenv:Body <cli:queryDocumentsResponse xmlns:cli=http://clientconnector.protocolterminator.openncp.epsos//> </soapenv:Body> </soapenv:Envelope> {code}
National Infrastructure doesn’t know how to interpret such response (lack of any context information).
We believe that this behavior on NCP-A concerning null interpretation is not accurate.
At least NCP-B behaviour shall be changed to respond with an error to the National Infrastructure, not with an empty reponse.
Following is the source code from server side concerning null interpretation:
!image-2023-04-11-13-12-09-302.png!