Cool, thanks for letting us know. Tammo
On 03.09.2010 14:54, Adnan wrote: > thx > solved > > -- > al > > > > > ________________________________ > From: Adnan <[email protected]> > To: [email protected] > Sent: Fri, 3 September, 2010 10:16:17 > Subject: Re: Problem when calling remote service > > Hello Tammo, > > I checked the soap messages and it seems the soap message is fine. with only > the > > difference in soap header. when i pasted the same soap message in soapUI > (with > header) that was sent by ode to axis2 service, it worked with out change... > Below are the soapUI and request from ode and response from axis2 service, > sniffed by TCPMon. > > > and process zip is attached to last email... i checked it thru Markmail. > thx. & waiting ... > > ============== > Listen Port: 8081 > Target Host: 127.0.0.1 > Target Port: 8888 > ==== Request ==== > POST /axis2/services/posttwitter HTTP/1.1 > Content-Type: text/xml; charset=UTF-8 > SOAPAction: "urn:postOnTwitter" > User-Agent: Axis2 > Host: 127.0.0.1:8081 > Transfer-Encoding: chunked > > 3a6 > <?xml version='1.0' encoding='UTF-8'?> > > <soapenv:Header> > > http://localhost:8081/axis2/services/posttwitter'>http://www.w3.org/2005/08/addressing";>http://localhost:8081/axis2/services/posttwitter > > > > urn:postOnTwitter'>http://www.w3.org/2005/08/addressing";>urn:postOnTwitter > > http://www.w3.org/2005/08/addressing/anonymous > </addr:ReplyTo> > > uuid:hqejbhcnphr5kaxgn58dfh'>http://www.w3.org/2005/08/addressing";>uuid:hqejbhcnphr5kaxgn58dfh > > > </soapenv:Header> > <soapenv:Body> > > ll'>http://twitter.soco";>ll > juj'>http://twitter.soco";>juj > > </postOnTwitter> > </soapenv:Body> > </soapenv:Envelope>0 > ==== Response ==== > HTTP/1.1 500 Erreur Interne de Servlet > Server: Apache-Coyote/1.1 > Content-Type: text/xml;charset=UTF-8 > Transfer-Encoding: chunked > Date: Thu, 02 Sep 2010 21:45:51 GMT > Connection: close > > 2b8 > <?xml version='1.0' encoding='UTF-8'?> > > > http://www.w3.org/2005/08/addressing/fault > <wsa:RelatesTo>uuid:hqejbhcnphr5kaxgn58dfh</wsa:RelatesTo> > <wsa:FaultDetail> > <wsa:ProblemAction> > <wsa:Action>urn:postOnTwitter</wsa:Action> > </wsa:ProblemAction> > </wsa:FaultDetail> > </soapenv:Header> > <soapenv:Body> > > <faultcode>wsa:ActionNotSupported</faultcode> > <faultstring>The [action] cannot be processed at the > receiver.</faultstring> > <detail /> > </soapenv:Fault> > </soapenv:Body> > </soapenv:Envelope> > 0 > > soapUI > ===== > > <soapenv:Header/> > <soapenv:Body> > <twit:postOnTwitter> > <!--Optional:--> > <twit:twitterID>asd</twit:twitterID> > <!--Optional:--> > <twit:twitterPassword>asd</twit:twitterPassword> > <!--Optional:--> > <twit:status>asd</twit:status> > </twit:postOnTwitter> > </soapenv:Body> > </soapenv:Envelope> > > > > -- > al > > > > > ________________________________ > From: Adnan <[email protected]> > To: [email protected] > Sent: Thu, 2 September, 2010 17:13:03 > Subject: Re: Problem when calling remote service > > > thx, am conf. the monitor... yea stacktrace is from axis and services are > implements in axis. > > > i dont know y the file is't being attached.. > > thx. > -- > al > > > > > ________________________________ > From: Tammo van Lessen <[email protected]> > To: [email protected] > Sent: Thu, 2 September, 2010 16:59:56 > Subject: Re: Problem when calling remote service > > Hi al, > > first off: the attachments didn't make it to the list and without them > it's quite difficult to follow. However, it looks like your receiver > does not understand the request. triggerActionNotSupportedFault is not > an ODE error but seems to occur with Axis2. Is your 2nd service > implemented with Axis2? It is good possible that this is not a > stacktrace produced by ODE but by the service you are calling and ODE is > just consuming this error message. > > Please try to use TCPMon to monitor the SOAP messages that are sent > through the wire and compare the message sent by ODE with messages sent > eg. via soapUI. > > HTH, > Tammo > > > On 02.09.2010 16:51, Adnan wrote: >> helloo.. >> >> any one?? >> >> thx >> >> -- >> al >> >> >> >> >> ________________________________ >> From: Adnan <[email protected]> >> To: Apache ODE Forum <[email protected]> >> Sent: Thu, 2 September, 2010 13:26:01 >> Subject: Problem when calling remote service >> >> >> Hello >> I'm getting an exception (mention in AXIS2 Console below) when calling a >> partner >> >> WS locally. First the process calls the remote service >> (http://ws.cdyne.com/WeatherWS/Weather.asmx?wsdl) and returns the soap >> result, > > >> which seems fine to me, when process invokes the 2nd service it shows >> triggerActionNotSupportedFault, BUT when I run the process with all the >> partner >> >> >> services on local machine, it runs fine. indivudually all Partner services >> are > > >> fine. >> >> >> ODE 1.3.4, AXIS2 1.5 >> Attached is the process. >> any idea plz. >> >> regards, >> al >> >> >> AXIS2 Console >> >> [WARN] triggerActionNotSupportedFault: messageContext: [MessageContext: >> logID=urn:uuid:2740AA3DC4EA6A4F6A1283425626408] problemAction: >> urn:postOnTwitter >> [ERROR] The [action] cannot be processed at the receiver. >> org.apache.axis2.AxisFault: The [action] cannot be processed at the receiver. >> at >> org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:373) >> >> ) >> >> at >> org.apache.axis2.addressing.AddressingFaultsHelper.triggerActionNotSupportedFault(AddressingFaultsHelper.java:336) >> >> ) >> >> .... >> >> BPEL Console >> >> INFO - ODEServer-2 - WatchDog.check(133) | [Properties for Endpoint: >> {http://twitter.soco}PostTwitter#PostTwitterHttpSoap11Endpoint] updated >> WARN - ODEServer-3 - SoapExternalService$4.call(492) | Fault response: >> faultType=(unkown) >> http://www.w3.o >> rg/2005/08/addressing">http://www.w3.org/2005/08/addressing/fault >> uuid:hqejbhcnphr5k9sjkhtm7v >> ltDetail><wsa:ProblemAction><wsa:Action>urn:postOnTwitter</wsa:Action></wsa:ProblemAction></wsa:FaultDetail></soapenv:Header><soapenv:Body><soapenv:Fault >> >> t >> xm >> lns:wsa="http://www.w3.org/2005/08/addressing";> wsa:ActionNotSupported The >> [action] cannot be processed at the receiver.</ >> faultstring><detail /></soapenv:Fault></soapenv:Body></soapenv:Envelope> >> ERROR - ODEServer-2 - INVOKE$2.onFailure(187) | Failure during invoke: >> INFO - ODEServer-2 - >> BpelRuntimeContextImpl.registerActivityForRecovery(1408) | >> >> >> ActivityRecovery: Registering activity 25, failure reason: on channel 44 >> >> >> > -- Tammo van Lessen - http://www.taval.de
