BPEL failed to invoke proxy server

parsaulian25.gmail.com's picture

Dear All,

I tried to invoke service through the ESB using the proxy service.

BPEL -> WSO2 ESB -> Endpoint service

But ODE BPEL failed to invoke the proxy service.
Proxy service can be accessed using soapUI.

The rrrors in the logs is as follows.
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "POST /services/sayHelloProxy.sayHelloProxyHttpSoap11Endpoint HTTP/1.1[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "Content-Type: text/xml; charset=UTF-8[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "SOAPAction: ""[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "User-Agent: Axis2[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "Transfer-Encoding: chunked[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "Host: localhost:8280[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.header] (ODEServer-11:) >> "[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> "31b[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> "<?xml version='1.0' encoding='UTF-8'?>http://localhost:8280/services/sayHelloProxy.sayHelloProxyHttpSoap11Endpointhttp://www.w3.org/2005/08/addressing/anonymousuuid:9f617ac1-c115-4c9b-a49c-e9da5087b448-3[\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> " Heloo world[\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> ""
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> "[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> "0"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> "[\r][\n]"
13:02:13,984 1646000 DEBUG [httpclient.wire.content] (ODEServer-11:) >> "[\r][\n]"
13:02:14,031 1646047 ERROR [org.apache.ode.axis2.ExternalService] (ODEServer-11:) Error sending message (mex={PartnerRoleMex#122 [PID {http://example.com/proxy/proses}proses-30] calling org.apache.ode.bpel.epr.WSAEndpoint@14c93d.sayHello(...)}): The server localhost failed to respond
org.apache.axis2.AxisFault: The server localhost failed to respond
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:389)
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:222)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:435)
at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at org.apache.ode.axis2.SoapExternalService$1$1.call(SoapExternalService.java:199)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.commons.httpclient.NoHttpResponseException: The server localhost failed to respond
at org.apache.commons.httpclient.HttpMethodBase.readStatusLine(HttpMethodBase.java:1976)
at org.apache.commons.httpclient.HttpMethodBase.readResponse(HttpMethodBase.java:1735)
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1098)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:550)
at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:189)
... 13 more
13:02:14,062 1646078 ERROR [org.apache.ode.bpel.runtime.INVOKE] (ODEServer-13:) Failure during invoke: Error sending message (mex={PartnerRoleMex#122 [PID {http://example.com/proxy/proses}proses-30] calling org.apache.ode.bpel.epr.WSAEndpoint@14c93d.sayHello(...)}): The server localhost failed to respond

I hope someone can solve this problem.

Thanks

rajika's picture

It seems that the ESB has

It seems that the ESB has failed to respond. Can you check if the ESB is getting the request and forwarding back the response? Just enable debug log level and check.

Rajika

parsaulian25.gmail.com's picture

Dear Rajika, Thank you for

Dear Rajika, Thank you for your responses. I find that the problem is the ESB can not recognize the WS-address headers in the SOAP request sent by ODEServer. The header is added to the SOAP request is as the following example: <soapenv:Header> <addr:To xmlns:addr="http://www.w3.org/2005/08/addressing">http://localhost:8280/services/sayHelloProxy.sayHelloProxyHttpSoap11Endpoint</addr:To> <addr:Action xmlns:addr="http://www.w3.org/2005/08/addressing"></addr:Action> <addr:ReplyTo xmlns:addr="http://www.w3.org/2005/08/addressing"> <addr:Address>http://www.w3.org/2005/08/addressing/anonymous</addr:Address> </addr:ReplyTo> <addr:MessageID xmlns:addr="http://www.w3.org/2005/08/addressing">uuid:95f8e805-fab1-4d69-9913-7225db165df5-4</addr:MessageID> </soapenv:Header> How can I make proxy service on the WSO2 ESB can ignore or process this header? Thanks
Hot Topic
Hot
Topic

Google Gadgets are a nice way to develop user interfaces for distributed services. The fact that they can be hosted anywhere over a network, not necessarily in the very portal server they eventually run in makes them re-usable and allows users to quickly...

Latest Webinar
In this webinar we'll share the range of concerns we've heard from the industry, and survey some of the new and sometimes subtle types of lock-in associated with cloud technologies.
Wednesday, 8 September, 10.00 AM (PDT)