You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Adnan <ad...@yahoo.com> on 2010/09/03 12:35:22 UTC
Problem when calling local service
Hello ,
I'm getting an error (mention in AXIS2 Console below) when calling a service
locally. The [action] cannot be processed at the receiver.
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 any change in
soap message...
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 ...
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))
==============
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 <ad...@yahoo.com>
To: user@ode.apache.org
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 <tv...@gmail.com>
To: user@ode.apache.org
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 <ad...@yahoo.com>
> To: Apache ODE Forum <us...@ode.apache.org>
> 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
>
>
>
Re: Problem when calling local service
Posted by "Demetris G. Galatopoullos" <de...@ece.neu.edu>.
Nice - thanks fhe info.
Quoting Adnan <ad...@yahoo.com>:
> i turned on the axis logs 2 more details, and saw tht sevice endpoint was not
> being sent correctly by bpel process, case sentivity problem.
>
> --
> al
>
>
>
>
> ________________________________
> From: D G <de...@ece.neu.edu>
> To: "java-user@axis.apache.org" <ja...@axis.apache.org>
> Cc: "java-user@axis.apache.org" <ja...@axis.apache.org>
> Sent: Sat, 4 September, 2010 3:18:44
> Subject: Re: Problem when calling local service
>
>
> How???
>
>
>
>
> On Sep 3, 2010, at 8:54 AM, Adnan <ad...@yahoo.com> wrote:
>
>
> thx.
> >solved
> >
> > --
> >al
> >
> >
> >
> >
> >
> ________________________________
> From: Adnan <ad...@yahoo.com>
> >To: axis-user@ws.apache.org
> >Sent: Fri, 3 September, 2010 12:35:22
> >Subject: Problem when calling local service
> >
> >
> >
> >
> >Hello ,
> >I'm getting an error (mention in AXIS2 Console below) when calling a service
> >locally. The [action] cannot be processed at the receiver.
> >
> >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 any change
> in
> >soap message...
> >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 ...
> >
> >
> > 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))
> >
> >
> >
> >==============
> >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 <ad...@yahoo.com>
> >To: user@ode.apache.org
> >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 <tv...@gmail.com>
> >To: user@ode.apache.org
> >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 <ad...@yahoo.com>
> >> To: Apache ODE Forum <us...@ode.apache.org>
> >> 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
> >>
> >>
> >>
> >
> >
> >
> >
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Problem when calling local service
Posted by Adnan <ad...@yahoo.com>.
i turned on the axis logs 2 more details, and saw tht sevice endpoint was not
being sent correctly by bpel process, case sentivity problem.
--
al
________________________________
From: D G <de...@ece.neu.edu>
To: "java-user@axis.apache.org" <ja...@axis.apache.org>
Cc: "java-user@axis.apache.org" <ja...@axis.apache.org>
Sent: Sat, 4 September, 2010 3:18:44
Subject: Re: Problem when calling local service
How???
On Sep 3, 2010, at 8:54 AM, Adnan <ad...@yahoo.com> wrote:
thx.
>solved
>
> --
>al
>
>
>
>
>
________________________________
From: Adnan <ad...@yahoo.com>
>To: axis-user@ws.apache.org
>Sent: Fri, 3 September, 2010 12:35:22
>Subject: Problem when calling local service
>
>
>
>
>Hello ,
>I'm getting an error (mention in AXIS2 Console below) when calling a service
>locally. The [action] cannot be processed at the receiver.
>
>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 any change in
>soap message...
>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 ...
>
>
> 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))
>
>
>
>==============
>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 <ad...@yahoo.com>
>To: user@ode.apache.org
>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 <tv...@gmail.com>
>To: user@ode.apache.org
>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 <ad...@yahoo.com>
>> To: Apache ODE Forum <us...@ode.apache.org>
>> 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
>>
>>
>>
>
>
>
>
Re: Problem when calling local service
Posted by D G <de...@ece.neu.edu>.
How???
On Sep 3, 2010, at 8:54 AM, Adnan <ad...@yahoo.com> wrote:
> thx.
> solved
>
> --
> al
>
>
> From: Adnan <ad...@yahoo.com>
> To: axis-user@ws.apache.org
> Sent: Fri, 3 September, 2010 12:35:22
> Subject: Problem when calling local service
>
>
> Hello ,
> I'm getting an error (mention in AXIS2 Console below) when calling a
> service locally. The [action] cannot be processed at the receiver.
>
> 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
> any change in soap message...
> 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 ...
>
>
> 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))
>
>
> ==============
> 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 <ad...@yahoo.com>
> To: user@ode.apache.org
> 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 <tv...@gmail.com>
> To: user@ode.apache.org
> 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 <ad...@yahoo.com>
> > To: Apache ODE Forum <us...@ode.apache.org>
> > 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
> >
> >
> >
>
>
>
>
Re: Problem when calling local service
Posted by Adnan <ad...@yahoo.com>.
thx.
solved
--
al
________________________________
From: Adnan <ad...@yahoo.com>
To: axis-user@ws.apache.org
Sent: Fri, 3 September, 2010 12:35:22
Subject: Problem when calling local service
Hello ,
I'm getting an error (mention in AXIS2 Console below) when calling a service
locally. The [action] cannot be processed at the receiver.
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 any change in
soap message...
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 ...
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))
==============
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 <ad...@yahoo.com>
To: user@ode.apache.org
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 <tv...@gmail.com>
To: user@ode.apache.org
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 <ad...@yahoo.com>
> To: Apache ODE Forum <us...@ode.apache.org>
> 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
>
>
>