HTTP Status-Code=400 (Bad Request) error for 2nd iteration for Java Over Http protocol
We are receiving the HTTP Status-Code=400 (Bad Request)for 2nd iteration and then script failing for Java Over Http Protocol.
The following are the Details
Operating System: Microsoft windows server 2003 standard edition service pack 2 RAM: 2GB Load Runner : 11 with Patch 04 Protocol: Java Over Http Business Scenario: Login and Logout of application.
It is a java based application which used java object serialization so we are using JOH protocol for script designing. we are using JNLP to record the application.
We are able to generate the script using LR 11 JOH protocol.
for this script, we have done correlation and script is running perfectly for first iteration and for second iteration it is failing at login step and giving the Bad Request error.
We have done our analysis from our end and observed during second iteration, while sending the request 10 (this request is for login part), it is appending/including the request 36 data also with request 10 so we are getting Bad Request error.
We are unable to understand why it is happing in second iteration only and how to over come this issue so we are seeking others help who can have knowledge and experience in such cases.
Re: HTTP Status-Code=400 (Bad Request) error for 2nd iteration for Java Over Http protocol
Thanks all for your suggestions.
In action part, it only contains log in and logout of application.
in the very response of request it is getting the server generated EXT unique identifier and passing that value in every further request so we have correlated that value and there are around 40 request XMLs for thse two login and logout steps.
as per your suggestion, we have commented that correlation function and executed the script but the output is same for second iteration : Bad Request
i was trying to upload that extended log script but could not able to upload since it is getting error similar to request timeout and tried many times from different machines
what else we can do to identify the root cause by writing any specific java code to get the maximum details in replay log?