DapIF Cannot Recognise End Of SOAP/XML Response When ASP Uses 'persistent Connection'
(Doc ID 1996940.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.
On Oracle Communication Network Charging & Control 5.0.2, dapIF cannot recognise end of SOAP/XML message when Data Access Pack is configured to keep the connection with the ASP open via the parameter :
The processing is stopped until the ASP closes the socket manually or after a timeout - Yet if no time-out is configured on the ASP side, the connection will remain blocked.
Testing scenario :
a) Generate a notification SLC->ASP
b) Received a response ASP->SLC. The response seems to be formatted correctly, in form of: HTTP headers + xml declaration + soap envelope.
c) After parsing http headers and xml declaration, dapIF hangs because can't identify next line which contains soap envelope. The DAP interface keeps on waiting until the ASP potentially closes the connection thanks to a possible timeout mechanism, usually set to approximately 30s.
d) The dapIF unblocks processing and reads+parse the soap enveloped. The call continues processing after 30 sec
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document