Script of Webservice is not sending timestamp in request in Load Runner 11
I am trying to run a test of web service in vugen of load runner 11, by webservice protocol. While running with extended logs on, it seems load runner is sending only one parameter of the webservice, but not timestamp, "profileTimestamp", and hence getting http 500 error.
When I created the script for this same webservice with http/html protocol, this same webservice call is successful.
Please help me understand why LR is not sending "profileTimestamp" in the request.
Script of web service protocol:
Output from Extended log:
Action.c(4): </soap:Header><soap:Body><isProfileStillValid xmls="http://....">
Action.c(4): <loginId xmlns="">CONYZ</login
Action.c(4): t=21594ms: 178-byte response headers for "http://..<actual url not provided here>....." (RelFrameId=1, Internal ID=1)
Action.c(4): HTTP/1.1 500 Internal Server Error\r\n
Thanks in advance
Couple of things looks suspicious:
1. Space between l and e in: isProfil eStillValid
2. No password required?
But any syntax error will often result in the ubiquitous 500 error, at least in my experiences with web service calls, as the developers are either lazy in pointing out the syntax error, or (claim) to keep mum for security reasons.
Space between l and e is error while editing in this forum. I rechecked, actual script doesn't have this space.
No Password require in this. This is an internal call between two applications. And more for this same webservice 'isProfileStillValid' when script is created using html/http protocol, it is running successfully.
But, not able to determine why "profileTimestamp=2015-04-09T11:35:29Z" is not showing as input parameter when I checked the extended replay logs in webservice protocol.
is the code you've pasted the request or the response? - it looks like a response to me and NOT the request - which may explain why you can't see the timestamp
do you need to dynamically set the timestamp? - how long before it becomes invalid?