Hi Team
i have recorded native application successfully but while validating script getting " NL_network-01" error.
Please find the below details:
Error Code: NL-NETWORK-01 Message: Network error: An IO error occurred sending the request. Details: java.io.EOFException: HttpConnectionOverHTTP@21cd6662(l:/10.80.35.141:55500 <-> r:genproxy.corp.amdocs.com/10.19.50.20:8080,closed=false)[HttpChannelOverHTTP@25f2e683(exchange=HttpExchange@60f06c59 req=TERMINATED/null@null res=PENDING/null@null)[send=HttpSenderOverHTTP@1b6e10a1(req=QUEUED,snd=COMPLETED,failure=null)[HttpGenerator@51da8bd8{s=START}],recv=HttpReceiverOverHTTP@63aea99e(rsp=IDLE,failure=null)[HttpParser{s=CLOSED,0 of 0}]]]
I tried below ways:
First: Without import certificate in preference.
Second: Unchecked HTTP/2 option under Recording Advanced option
Third: uploaded certificate in preference. but when click start recording getting error"An Error occurred when loading neoload certificate "(SSL Error)
Ok you're right the HTTP 400 is not related to the network issue. Regarding if it's HTTP/1.1 or HTTP/2 it can't be HTTP/2 since your URL is not HTTPS but HTTP. So that's not either the issue.
However i noticed something that could be the root cause of the network error in NeoLoad. In your POST request could you look at the HTTP headers in the Design section available when you hit the "Advanced" button of your request. Then remove the "connection: close" HTTP header from the list of headers.
Try again the replaying of your user path.
Did you find this useful ?
0% of users found this answer useful
You should revert back your modifications about the certificate in the NeoLoad preferences. Your issue is not related to that.
The network error is a kind of connection reset. Before that request you get another error which is an HTTP 400 bad request. The network error might be a consequence of that previous error.
First of all check in the recorded response if you got something from the server to make sure that it's not an error that already occurred during the recording.
Then try to fix first the HTTP 400 error to see if it also fixes that network error.
HI Nouredine
Thank you for your quick Answer.
400 bad request is for Facebook URL(POST https://graph.facebook.com/v3.2/827895287262557/activities HTTP/1.1) . that is not application URL..
First itself Nl- NETWORK-01 error. i tried multiple times.
Please check one more time. Find the attached screen shot.
If you see in second screen shot in recorded request HTTP/1.1 and response it not showing which protocol using either HTT/1.1 OR 2. if HTTP2 protocol.. it might be issue.
Can you please check and confirm what is the issue.
Hi Nouredine
I deleted Connection: Close. Script is working fine.
Its AWESOME.
Thanks you very much for your help.
Do you have any idea Why this header is recorded like this? is this application issue or something else
I can't tell if it's an application issue or expected. That header will tell the server to close the connection after sending the response. That means that it's not a keep-alive connection. It's not efficient but it may be done on purpose.
On NeoLoad side this close connection is not properly handled.
Nouredine was made best respondent
Nouredine answered
Nouredine was made best respondent
Allabhakshu answered
Nouredine answered
Allabhakshu answered
Nouredine was made best respondent
Nouredine answered
Allabhakshu posted a new question
