I'm new to axis myself, but I have been investigating some memory leak problems. Through looking for that, I found out that the Call object contains everything, for lack of a better word, to send and receive the data, so if you want concurrency, you have to create seperate call objects for that. But, you can reuse those objects for the same client, which may save you some resources.
Jennifer Jackson Programmer/Analyst -----Original Message----- From: Haug Thomas [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 2:50 AM To: '[EMAIL PROTECTED]' Subject: AW: Concurrent usage of the Call object ? Hi Jennifer and Sumit, thanks for your advise: this is exactly what I have already suspected. So my question shifts a little bit : if a client wants to issue several requests concurrently, is it sufficient to create a separate Call object for each thread ? HAs anybody tried that before ? Thanks, Thomas > -----Urspr�ngliche Nachricht----- > Von: Jackson, Jen (CCI-Atlanta) [mailto:[EMAIL PROTECTED] > Gesendet am: Montag, 30. Juni 2003 14:32 > An: [EMAIL PROTECTED] > Betreff: RE: Concurrent usage of the Call object ? > > Hi Thomas. My understanding is that the Call object is a > stateful object, containing the soap request and response. > The Serializer and Deserializers contains the request and > response data within the call object. So I would say you > need to create a call per soap request. > > Anyone else? > > Jennifer Jackson > Programmer/Analyst > > -----Original Message----- > From: Haug Thomas [mailto:[EMAIL PROTECTED] > Sent: Monday, June 30, 2003 8:27 AM > To: '[EMAIL PROTECTED]' > Subject: Concurrent usage of the Call object ? > > > Hi everbody, > > I have a question regarding the org.apache.axis.client.Call > class. Is it > possible that a client creates only one Call instance and than issues > serveral requests through this object concurrently or is this > kind of usage > illegal ? > > Thanks, > Thomas >
