RE: concurrent call.invoke problem

[Heitzeg, Bill]

What was the difference in performance?  Also, what does your handler look like?     -----Original Message----- From: GANDHIRAJAN,AYYAPPAN (HP-India,ex2) [mailto:[EMAIL PROTECTED] Sent: Monday, February 16, 2004 2:14 AM To: '[EMAIL PROTECTED]' Subject: RE: concurrent call.invoke problem   Hi Bill and Tony,   Thanks for your responses!!! At last, I found the problem and I thought i can share my experience with you folks.   In my last mail, I said I was using a simple hello world service. But the fact is that the service was also having a handler:)    The service contains a handler and a back end componet. And the execution flow will be like this 1) Invoke the handler 2) Invoke the back end component. 3) And finally back end component invokes another webservice.   After carried out a lot of investigation in many parts of my program, I removed the handler part and had only step 2 and step 3. Now the performance is too good.   Here is my wsdd   <service name="HelloWorld" provider="java:RPC">   <requestFlow>    <handler type="java:handler.MyHandler"/>   </requestFlow>   <parameter name="allowedMethods" value="*"/>   <parameter name="scope" value="Application"/>    <parameter name="className" value="tests.HellowWorld"/>   <namespace>http://tempuri.org/</namespace>  </service>   Again, I am throwing a question. Why doesn't Axis scale to multiple clients when there is a handler inside the axis soap service.     Thanks & regards, Ayyappan Gandhirajan ---------------------------------------- Senior Software Engineer, NSP BU, HP Services - Offshore, Office: 91.80.225.1554 Ext 1472 Direct: 91.80.205.1472 Telnet: 847.1472 Mobile: 91.94483.14969 E-Mail: [EMAIL PROTECTED] ---------------------------------------- -----Original Message----- From: Tony Blair [mailto:[EMAIL PROTECTED] Sent: Sunday, February 15, 2004 11:45 PM To: [EMAIL PROTECTED] Subject: Re: concurrent call.invoke problem Hi there,   Have you played around with service scope? Perhaps if your Service is stateless then set the scope to "Application" to reduce the amount of the object creation. By default Axis set the scope to "Request" which cause the object creation to increase. Of course I am not sure if this is root of your problem. Just a thought.   Regards, Tony. "GANDHIRAJAN,AYYAPPAN (HP-India,ex2)" <[EMAIL PROTECTED]> wrote: Hi guys, I have already posted this question. Could you please throw some light on this. I have deployed a simple "Hello world" soap service in axis in weblogic 8.1. And I have tried to invoke it using 5 concurrent clients for 10 times each. Surprisingly, the invocation time for each transaction has increased to more than 5 times. Average time for invocation for 1 client for 10 times ---> ~50 msec Average time for invocation of the same service for 5 clients for 10 times --->~600msec Could you please tell me as to where it went wrong and tips to improve the performance? Are there any document regarding this? Thanks in advance. Regards, Ayyappan Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online