DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40757>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40757

           Summary: Web Service(SOAP) Request Response Time
           Product: JMeter
           Version: 2.2
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: major
          Priority: P3
         Component: Main
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


I was doing load testing against XFire and AXIS (deployed on JBoss 4.0.1SP1). 
I used both JMeter and SOAPUI to measure response time, but the result is quite
different. SOAPUI says it takes about 10ms, while JMeter think it takes 200ms. 
I checked the reponse, both SOAPUI and JMeter did get the right response back.

Finally, I got wireshark and captured the packets on wire. And here is what I
observed: when using JMETER, The HTTP request was segmented into two packets.
There was a significant delay (about 200ms) between the first segment and the
ACK. After the server got 2nd packet, it only took 5 ms to send a response back.

After some research, I realize that JMeter is using Apache SOAP, which seems
handle HTTP request by itself instead of using commons-httpclient. I am guessing
 the improper HTTP handling in Apache SOAP is the root cause. I know Apache SOAP
is not supported anymore and you are planning to move to another SOAP stack. So
hopefully my observation give you another reason to move since the whole Web
Service(SOAP) sampler wont be able to provide accurate measurement at all.

Let me know if you need any more information. I have the screen shot of
wireshark and also the captured packets in pcap format . I dont know how to
upload though.

Thanks for your help,
Fei

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to