On 21/03/06, Erik Lindegren <[EMAIL PROTECTED]> wrote: > Hi, > > I finally found the problem, and of course it didn't have anything to > do with jmeter :) The problem was that the computer I was running my > apache server on had ip connection tracking enabled. It has an upper > limit on how many connections it can track, and I exceeded that for > some reason when I used two jmeter-servers. The strange thing is that > I never saw the problem when I run one jmeter-server, even if I > managed to load the server just as much as I did with two?
The default HTTP protocol implementation does its own connection pooling. It's likely that two pools will need more connections than one. > > You may find the upper limit here: > > cat /proc/sys/net/ipv4/ip_conntrack_max > > I just turned the ip connection tracking off, and the problem > disappeared. The ip_conntrack was built as a module on my system so I > turned it off by removing the ip_conntrack.o file. > > The reason why I didn't find this problem earlier is that I don't > have root privileges on my machines, so I had to get hold of a person > who has. And after having a look in the messages log file, the > problem was more obvious. > > Thank you for all your help! > Thanks for letting us know the problem has been resolved. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
