Jai,
I m using a threaded program to get 50 concurrent requests
to my webservice. I enabled the axis logging and ran my program. The
axisServlet was called concurrently(log time indicated that) . so I assumed that
there is no network problem.Then onwards each thread started taking its own time
and when it reached my web service, only few threads were concurrent. I went
thro the log created by axis and found that till de- serializationimpl all the
threads were having same time consumption. Then they differed and every next
thread took more and more time. Then I tuned my server for accepting more
concurrent threads and also increased heap.But there was no difference in
result. Can you suggest me some other ways...
thanks
aravind
-----Original Message-----
From: THOMAS, JAI [AG-Contractor/1000] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 15, 2004 1:57 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Slow deserialization in axisAravind,Our server does both serializations (but more bean) and we haven't noticed any significant performance problems with heavy loads.Now, how are you determining deserialization is the problem? It can be caused by varous factors such as your network configuration,app server scalability etc..-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 15, 2004 1:48 PM
To: [EMAIL PROTECTED]
Subject: RE: Slow deserialization in axisIts bean serialization. I m using default setup of axis without changing anything.aravind-----Original Message-----
From: THOMAS, JAI [AG-Contractor/1000] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 15, 2004 1:45 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Slow deserialization in axisAre you using bean or custom serialization?Jai-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 15, 2004 12:53 PM
To: [EMAIL PROTECTED]
Subject: Slow deserialization in axisHi,
I have hosted a webservice using axis on tomcat 4.1.24.
I m finding that as concurent load increases, there is a tremendous growth in the deserialization time taken.
Any clues ??
Thanks
aravind
