l: [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
-From: Tony Blair
[mailto:[EMAIL PROTECTED]Sent: Sunday, February 15, 2004 11:45
PMTo: [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&
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 roo
he results.
Bill Heitzeg.
-Original Message-
From: GANDHIRAJAN,AYYAPPAN (HP-India,ex2)
[mailto:[EMAIL PROTECTED]
Sent: Sunday, February 15, 2004 1:08 AM
To: '[EMAIL PROTECTED]'
Subject: concurrent call.invoke problem
Hi guys,
I have already posted this question. Could you please throw som
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