it looks like the webservice binding wasn't found on the server side. double check the test plan to make sure the settings are correct.
peter On 1/30/06, Fan, Jenny <[EMAIL PROTECTED]> wrote: > > Here is the full response text: > <?xml version="1.0" encoding="utf-8"?><soap:Envelope > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"; > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse > curity-secext-1.0.xsd" > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec > urity-utility-1.0.xsd"><soap:Header><wsa:Action>http://schemas.xmlsoap.o > rg/ws/2004/08/addressing/fault</wsa:Action><wsa:MessageID>urn:uuid:75988 > 76f-aeb6-403c-83bd-7cee0dbf691c</wsa:MessageID><wsa:RelatesTo>urn:uuid:a > a54d875-5f1c-428c-99eb-dfa9ab51653e</wsa:RelatesTo><wsa:To>http://schema > s.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsse:Securit > y><wsu:Timestamp > wsu:Id="Timestamp-1231794e-a6f0-4ff2-9f4d-8728614523bb"><wsu:Created>200 > 6-01-30T21:06:08Z</wsu:Created><wsu:Expires>2006-01-30T21:11:08Z</wsu:Ex > pires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><soap:Fau > lt><faultcode>soap:Server</faultcode><faultstring>Server was unable to > process request. ---> The requested exception policy > 'TorstarDigital.Tops.Web.Services.Utility.LookupHelper' could not be > found.</faultstring><detail /></soap:Fault></soap:Body></soap:Envelope> > > Thanks, > > Jenny > > -----Original Message----- > From: Peter Lin [mailto:[EMAIL PROTECTED] > Sent: Monday, January 30, 2006 4:07 PM > To: JMeter Users List > Subject: Re: Got fault code in web service response > > what else do you see in the result tree? > > specifically, http header response codes and other details in the soap > response message? > > peter > > > On 1/30/06, Fan, Jenny <[EMAIL PROTECTED]> wrote: > > > > Hi Peter, > > > > I am testing another web service method and getting the fault code > > again. This method is similar to the previous one (base64 encoded). I > > tried to use view result tree, but it still doesn't work this time. > The > > method works fine with soap scope. Any suggestion? > > > > > <soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Se > > rver was unable to process request. ---> The requested exception > > policy 'TorstarDigital.Tops.Web.Services.Utility.LookupHelper' could > not > > be found.</faultstring><detail /></soap:Fault></soap:Body> > > > > Thanks a lot, > > > > Jenny > > > > -----Original Message----- > > From: Peter Lin [mailto:[EMAIL PROTECTED] > > Sent: Monday, January 30, 2006 2:11 PM > > To: JMeter Users List > > Subject: Re: Got fault code in web service response > > > > well any bugs in the SOAP webservice sampler is my fault, since I > wrote > > it > > :) > > > > glad that helped > > > > peter > > > > > > On 1/30/06, Fan, Jenny <[EMAIL PROTECTED]> wrote: > > > > > > Hi Peter, > > > > > > No, I tried it in aggregate report. Now I add View result tree > report, > > > it works. You rock!!! It's strange to me that the result content > > > recorded differently in different listener. > > > > > > Thanks, > > > > > > Jenny > > > > > > -----Original Message----- > > > From: Peter Lin [mailto:[EMAIL PROTECTED] > > > Sent: Monday, January 30, 2006 1:57 PM > > > To: JMeter Users List > > > Subject: Re: Got fault code in web service response > > > > > > apache soap supports base64 encoding, but the current SOAP > webservice > > > sampler doesn't really do anything special with base64 encoded data. > > > are > > > you trying to view the result in the result tree? > > > > > > peter > > > > > > > > > On 1/30/06, Fan, Jenny <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi Guys, > > > > > > > > > > > > > > > > I just started using JMeter to test web service request. It did > work > > > > with some sample web services. But I got error message in the > > > responses > > > > when testing a web service which include a base64 encoded in > > response. > > > > The web service works fine with soap scope. > > > > > > > > Response I get in soap scope: > > > > ...<soap:Body> > > > > + <javascript:showNode('1.1.2.1');> <GetDomainsResponse > > > > <http://localhost:7103/tide/main/[EMAIL PROTECTED]:> > > > > xmlns="http://cmsservices.torstardigital.com/Tops2.0";> > > > > + <javascript:showNode('1.1.2.1.1');> > > > > > > > > > > <GetDomainsResult>77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbm...</GetDomainsResul > > > > t> > > > > </GetDomainsResponse> > > > > </soap:Body>.. > > > > Response I get in JMeter: > > > > > > > > ... > > > > > > > > > > ><soap:Body><soap:Fault><faultcode>soap:Server</ > > > > faultcode><faultstring>Server was unable to process > > request. > > > > ---&gt; The given key was not present in the > > > > dictionary.</faultstring><detail > > > > /></soap:Fault></soap:Body><... > > > > > > > > > > > > > > > > Any idea what's the cause? > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > > > Jenny > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
