Re: Multi-threaded soap call issue.
"Scott Nichol" <[email protected]> Thu, 19 Aug 2004 10:27:38 -0400
| Newsgroups | gmane.text.xml.soap.devel |
|---|---|
| Message-ID | <048401c485f8$ae60ce60$6401a8c0@northgate> |
I suspect the problem is in your client code. The Call class is not thread safe. For a multithreaded client, each thread should have its own Call instance. Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. ----- Original Message ----- From: <[email protected]> To: <[email protected]>; <[email protected]> Sent: Wednesday, August 18, 2004 6:08 PM Subject: Multi-threaded soap call issue. > Hello, > > We have a web service running on IBM Websphere. > > It seems to be working fine and multiple clients are able to access it. I > have a strange problem though. > > > When a multi-threaded client program invokes it (having around 50 threads > and making multiple calls on the same thread), then > sometimes I get a "java -- no signature match" exception. When i looks at > the input call, it seems to be that the parameters of 3 - 4 > calls are present in the same call (the same parameters are repeated over > and over for the single call) > > My question is this. > > 1. Does soap have some limitation with multi-threading? > > 2. Is there some setting i need to have in websphere to overcome this? > > Please let me know. Any help would be appreciated. > > Regards, > Srikanth > > This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. > >