>-----Original Message----- >From: Angel Orts [mailto:[EMAIL PROTECTED] >Sent: 16 February 2004 15:37 >To: [EMAIL PROTECTED] >Subject: Re: bottleneck on JMeter clients - distributed test > > >Jordi and Sebastian, thanks for your quick answers. >Unfortunately HTTP is >not an option at the moment. I can't test HTTP. Regarding RMI, >I wonder how >much traffic there should be when no listeners are enabled. >Doesn't seem >significative to me. >
Ah, but JMeter adds a Remote listener to the test plan before it copies it to the remote client. Also, we had a problem with RMI chewing CPU - admittedly, it was an early release of a JVM on OpenVMS - but it seems to me that it would be worth checking whether RMI makes any difference. If this does not help, I suppose it might be worth trying to run as similar a test as possible using dummy http pages instead. If you don't have any HTTP servers available, I suppose JavaTest samplers could be used instead - if that showed a problem, it would indicate a bug in JMeter or the setup... S. ___________________________________________________________________________ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. ___________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
