Home > Archive > Software Testing > January 2006 > Loadrunner: win socket buffer corrupt
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Loadrunner: win socket buffer corrupt
|
|
| ryanren@gmail.com 2006-01-12, 3:59 am |
| It's a win socket script recorded by loadrunner.
lrs_receive(), when pressure is higher, the loadrunner will receive
some corrupted buffer contrasting EXPECTED BUFFER, e.x.
vuser_init.c(31): lrs_send(socket1, buf4) [MsgId: MMSG0]
vuser_init.c(33): lrs_receive(socket1, buf5) [MsgId: MMSG0]
vuser_init.c(33): Mismatch (expected 522 bytes, 31 bytes actually
received) [MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3DEXPECTED
BUFFER=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D [MsgId: MMSG0]
"\n"
"Terminal type set to EBS-GUI\n"
"\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"&START&3"
"\xfe"
"20=EF=A8=8DWAITING APPLICATION&END&&START&99"
"\xfe"
"40=EE=93=85"
"\xfe"
"10,"
"\xfe"
"22 OCT 2005 12:48=EE=A0=AC15.0.00=EE=A0=B705.003&END&"
[MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
[MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3DRECEIVED
BUFFER=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D [MsgId: MMSG0]
"\n"
"Terminal type set to EBS-GUI\n"
"\n"
[MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
[MsgId: MMSG0]
vuser_init.c(33): callRecv:31 bytes were received [MsgId: MMSG0]
vuser_init.c(36): lrs_send(socket1, buf6) [MsgId: MMSG0]
vuser_init.c(36): Notify: Parameter Substitution: parameter "pSdUser" =3D
"USER45" [MsgId: MMSG-13992]
vuser_init.c(38): lrs_receive(socket1, buf17) [MsgId: MMSG0]
vuser_init.c(38): Mismatch (expected 159 bytes, 198 bytes actually
received) [MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3DEXPECTED
BUFFER=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D [MsgId: MMSG0]
"&START&30~67~*** YOUR MAINTENANCE FEES ARE OVERDUE (20051230)
***~~CONTINU"
"E~~~20&END&&START&99~56~03 JAN 2006~USER.1~3,~10 JAN 2006
07:08~g15.0.00~r"
"05.003&END&"
[MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
[MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3DRECEIVED
BUFFER=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D [MsgId: MMSG0]
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
"PTERM: No such file or directory\n"
[MsgId: MMSG0]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
[MsgId: MMSG0]
I wanna find a function in loadrunner, which can continue receiving
socket buffer till the ending flag string appear. In last example, the
ending flag is "05.003&END&". But the first and the second RECEIVED
BUFFER didn't finish receiving the EXPECTED BUFFER, and they didn't
finish by "05.003&END&".
Could you please give me some advice?
Many thanks.
| |
| ryanren@gmail.com 2006-01-12, 3:59 am |
| I have found a func:
lrs_set_receive_option(EndMarker, BinaryStringTerminator,
"05.003&END&", LrsLastArg);
But it affect only thing that will finish receive when a ending flag
appear, but not waiting for a ending flag.
|
|
|
|
|