RE: Is axis client session handling thread safe ?

[Paul.Smith3]

Title: Message

Is it possible that sometimes the second thread request is getting executed before the first thread request has set the appropriate value in the session?   In other words, how does your second thread know that the first thread has sucessfully put something in the session? Paul Smith -----Original Message----- From: Carpe Sebastien [mailto:[EMAIL PROTECTED] Sent: 26 October 2005 17:28 To: axis-user@ws.apache.org Subject: Is axis client session handling thread safe ? Here is my problem : I'm having a client that does 2 WS requests (the first sets something in the session, the seconds returns it). All is set and works nicely, as long as i have a single Threaded client. Now, i get my client and multi-threads it (this client will actually be used as a proxy between a binary protocole and a webservice access). And then everything goes boo : some times, not every time, the second requets go berserk, finding nothing within the session. NB : the service and call objects are local to each thread (service built once, call built on each call -tried to keep a single call object, but it didn't help either on keeping session) Done some tcpmon logging, and it appears that the 2nd request sometimes doesn't have any cookie send (this is http session cookie based). The whole stuff does not bail out the same way twice, so it seems to be a thread-safe related issue. I've tried to hack around the axis code and see if i could find any good track, but in vain .... I'm using axis 1.2.1 (tried axis 1.3, but it did not do any difference). Any help appreciated... Seb C. ------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------