catalina oancea wrote:
Hi,
Thanks for the idea.
What I see using strace is that normal sendto looks like this:
sendto(14, "\...@$&\0\264>z\200\0\31\345\0'\273T\21S3\17vvswwvwsvy}\376"...,
180, MSG_DONTWAIT, {sa_family=AF_INET, sin_port=htons(9764),
sin_addr=inet_addr("192.168.12.12")}, 16) = 180
sendto(14,
"\...@$&\0\264-Q\200\0\31\346\0'\273\364\21S3\17~\177\374\375\375\376\376\374\371\367\372\366"...,
180, MSG_DONTWAIT, {sa_family=AF_INET, sin_port=htons(9764),
sin_addr=inet_addr("192.168.12.12")}, 16) = 180
sendto(14,
"\...@$&\0\264\26=\200\0\31\347\0'\274\224\21S3\17\177}\177\375\374\376\376\372\374\177\375\373"...,
180, MSG_DONTWAIT, {sa_family=AF_INET, sin_port=htons(9764),
sin_addr=inet_addr("192.168.12.12")}, 16) = 180
sendto(14, "\...@$&\0\264\263\35\200\0\31\350\0'\2754\21S3\17qxyvtvy~}x~|"...,
180, MSG_DONTWAIT, {sa_family=AF_INET, sin_port=htons(9764),
sin_addr=inet_addr("192.168.12.12")}, 16) = 180
sendto(14,
"\...@$&\0\264?\347\200\0\31\351\0'\275\324\21S3\17\364\364\365\371\370\365\364\363\363\365\371\367"...,
180, MSG_DONTWAIT, {sa_family=AF_INET, sin_port=htons(9764),
sin_addr=inet_addr("192.168.12.12")}, 16) = 180
And the one that causes the error looks like this:
sendto(14,
"\...@$&\0\264T\234\200\0\31\352\0'\276t\21S3\17xyuy}\377\374\367\373\376\372\373"...,
180, MSG_DONTWAIT, {sa_family=0x2e32 /* AF_??? */,
sa_data="168.13.13\r\nCSe"}, 16) = -1 EAFNOSUPPORT (Address family not
supported by protocol)
Is this a bug in the way the parameters are sent?
To me this looks like a bug (assuming you properly compiled and linked
sipp). Why don't you add some logging around the failing syscall and
figure out what went wrong?
BR, Dmitry
You can run sipp under strace and find out which particular syscall fails.
Just run strace -ff -o strace.log sipp ...
Where ... should be replaced with sipp args.
Then read and analyze the strace log files.
I would also try to increase the number of open file descriptors per
process. Like this ulimit -n <some big number>.
HTH, Dmitry
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
