You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Manoj Dhirde <md...@incognito.com> on 2011/11/10 15:46:05 UTC
Transport Sender Invoke Failed
Hi Guys,
We are putting together a C++ API for a WebService. We have generated
c-stubs from the wsdl for client and generated the server side code in
Java. Now when we send request from our API to the Java WebService we get
following error,
[Thu Nov 10 06:35:17 2011] [debug] http_transport_sender.c(805) using axis2
native http sender.
[Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
msg_ctx_id:urn:uuid:3586181c-0ba9-1e11-3b20-0026b94edeb5
[Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442) Error occurred in
transport
[Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport sender invoke
failed
Then to check with python, we generated the server side stubs in python and
started the Python WebService and it processes request successfully from
the C++ API through same c stubs client.
Not sure why its not working with Java WebService as our preference is for
Java for the Server side.
Any help is greatly appreciated.
Thanks,
--
*Manoj Dhirde*
Senior Developer
*P:* 604-688-4332x808
*E:* mdhirde@incognito.com
*Toll-Free:* 1-800-877-1856
*F:* 604-688-4339
*VoIP:* sip:808@sip.incognito.com
[image: Incognito Software Inc.] <http://www.incognito.com>
<http://www.incognito.com/company/events>
Re: Transport Sender Invoke Failed
Posted by Manoj Dhirde <md...@incognito.com>.
Thanks Damitha,
I will try your suggestions and will update you about the outcome.
Regards,
Manoj Dhirde.
On Mon, Nov 14, 2011 at 11:36 AM, Damitha Kumarage <da...@wso2.com> wrote:
> Hi Manoj,
> Please note that the media type for SOAP 1.1 is |text/xml| and for SOAP
> 1.2 is |application/soap+xml|.
> Also instead of SOAP 1.1 mandatory |SOAPAction| HTTP header, an optional
> |action| parameter on the |application/soap+xml| media type
> is introduced in SOAP 1.2.
> Try changing those appropriately in your request.
>
> Thanks,
> Damitha
> Manoj Dhirde wrote:
>
>> Hi Damitha,
>>
>> Following are the contents of the header for each request,
>>
>> *C++ API talking to Python WebService through client built with c-stubs
>> from the wsdl:*
>>
>> POST /services/ShService HTTP/1.1
>> User-Agent: Axis2C/1.6.0
>> SOAPAction: "http://www.metaswitch.com/**ems/soap/sh/Sh/ShPull<http://www.metaswitch.com/ems/soap/sh/Sh/ShPull>
>> "
>> Content-Length: 417
>> Content-Type: text/xml;charset=UTF-8
>> Host: 192.168.75.109:8081 <http://192.168.75.109:8081>
>>
>> *C++ API talking to Java WebService through client built with c-stubs
>> from the wsdl:*
>> *
>> *
>> POST /MetaSwitchSimulator/services/**ShService HTTP/1.1
>> User-Agent: Axis2C/1.6.0
>> SOAPAction: "http://www.metaswitch.com/**ems/soap/sh/Sh/ShPull<http://www.metaswitch.com/ems/soap/sh/Sh/ShPull>
>> "
>> Content-Length: 417
>> Content-Type: text/xml;charset=UTF-8
>> Host: 192.168.75.109:2800 <http://192.168.75.109:2800>
>>
>> I will check the Server implementation again, the only change we added on
>> top of the generated stubs in case both servers was to send back success
>> response and nothing else was changed. But as suggested by you, I will
>> double check the server implementation.
>>
>> I changed the SOAP version of client as well thinking that could have
>> caused the issue with Java WebService, I changed it from 1.1 to 1.2 but
>> still same error.
>>
>> Thanks,
>>
>> Manoj Dhirde.
>>
>>
>> On Fri, Nov 11, 2011 at 11:38 AM, Damitha Kumarage <damitha@wso2.com<mailto:
>> damitha@wso2.com>> wrote:
>>
>> Hi Manoj,
>> Server send back a soap fault where it does not give details of
>> the problem that occured.
>> Can you also send us the http headers of your request for both
>> cases as well. Most probably this could be due to differences in
>> the content type or
>> action headers that the client send.
>> Also double check your service implementation in java. The soap
>> fault could also result due to an error thrown from your service.
>>
>> Thanks,
>> Damitha
>> Manoj Dhirde wrote:
>>
>> Hi Damitha,
>>
>> Thanks for looking into this.
>>
>> Following are the request/responses in case of a Python
>> WebService and Java WebService, when a request was sent
>> through a client built through c-stubs.
>>
>> *C++ API talking to Python WebService through client built
>> with c-stubs from the wsdl:*
>>
>> *Request:*
>> /<soapenv:Envelope
>> xmlns:soapenv="http://schemas.**xmlsoap.org/soap/envelope/<http://schemas.xmlsoap.org/soap/envelope/>"
>> xmlns:sh="http://www.**metaswitch.com/ems/soap/sh<http://www.metaswitch.com/ems/soap/sh>
>> ">/
>> / <soapenv:Header/>/
>> / <soapenv:Body>/
>> / <sh:ShPull>/
>> / <sh:UserIdentity>MySwitch/ABC
>> Corporation</sh:UserIdentity>/
>> / <sh:DataReference>0</sh:**DataReference>/
>> / <sh:ServiceIndication>Meta_**
>> BusinessGroup_CallPark</sh:**ServiceIndication>/
>> / <sh:OriginHost>mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> <http://mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> >
>> <http://mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> ></sh:**OriginHost>/
>> / </sh:ShPull>/
>> / </soapenv:Body>/
>> / </soapenv:Envelope>/
>> /
>> /
>> *Response:*
>> HTTP/1.0 200 OK
>> Server: ZSI/1.1 BaseHTTP/0.3 Python/2.5.2
>> Date: Fri, 11 Nov 2011 03:12:54 GMT
>> Content-type: text/xml; charset="utf-8"
>> Content-Length: 878
>>
>> <SOAP-ENV:Envelope
>> xmlns:SOAP-ENC="http://**schemas.xmlsoap.org/soap/**encoding/<http://schemas.xmlsoap.org/soap/encoding/>
>> "
>> xmlns:SOAP-ENV="http://**schemas.xmlsoap.org/soap/**envelope/<http://schemas.xmlsoap.org/soap/envelope/>
>> "
>> xmlns:ZSI="http://www.zolera.**com/schemas/ZSI/<http://www.zolera.com/schemas/ZSI/>
>> "
>> xmlns:xsd="http://www.w3.org/**2001/XMLSchema<http://www.w3.org/2001/XMLSchema>
>> "
>> xmlns:xsi="http://www.w3.org/**2001/XMLSchema-instance<http://www.w3.org/2001/XMLSchema-instance>
>> ">
>> <SOAP-ENV:Header></SOAP-ENV:**Header>
>> <SOAP-ENV:Body xmlns:ns1="http://www.**metaswitch.com/ems/soap/sh<http://www.metaswitch.com/ems/soap/sh>
>> ">
>> <ns1:ShPullResponse>
>> <ns1:ResultCode>200</ns1:**ResultCode>
>> <ns1:ExtendedResult>
>> <ns1:ExtendedResultCode>100</**ns1:ExtendedResultCode>
>> <ns1:ExtendedResultDetail>**SUCCESS</ns1:**
>> ExtendedResultDetail>
>> <ns1:ExtendedSubResults>
>> <ns1:SubResult>
>> <ns1:SubResultCode>100</ns1:**
>> SubResultCode>
>> <ns1:SubResultDetail>SUCCESS</**
>> ns1:SubResultDetail>
>> <ns1:SubResultSource>**
>> MetaSwitch.com</ns1:**SubResultSource>
>> </ns1:SubResult>
>> </ns1:ExtendedSubResults></**ns1:ExtendedResult>
>> </ns1:ShPullResponse>
>> </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> *C++ API talking to Java WebService through client built with
>> c-stubs from the wsdl:*
>> *
>> *
>> *Request:*
>> *
>> /<soapenv:Envelope
>> xmlns:soapenv="http://schemas.**xmlsoap.org/soap/envelope/<http://schemas.xmlsoap.org/soap/envelope/>"
>> xmlns:sh="http://www.**metaswitch.com/ems/soap/sh<http://www.metaswitch.com/ems/soap/sh>
>> ">/
>> / <soapenv:Header/>/
>> / <soapenv:Body>/
>> / <sh:ShPull>/
>> / <sh:UserIdentity>MySwitch/ABC
>> Corporation</sh:UserIdentity>/
>> / <sh:DataReference>0</sh:**DataReference>/
>> / <sh:ServiceIndication>Meta_**
>> BusinessGroup_CallPark</sh:**ServiceIndication>/
>> / <sh:OriginHost>mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> <http://mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> >
>> <http://mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> ></sh:**OriginHost>/
>> / </sh:ShPull>/
>> / </soapenv:Body>/
>> / </soapenv:Envelope>/
>> /
>> /
>> *
>> *Response:*
>> HTTP/1.1 500 Internal Server Error
>> Server: Apache-Coyote/1.1
>> Content-Type: text/xml;charset=UTF-8
>> Transfer-Encoding: chunked
>> Date: Fri, 11 Nov 2011 03:15:57 GMT
>> Connection: close
>>
>> <?xml version='1.0' encoding='UTF-8'?><soapenv:**Envelope
>> xmlns:soapenv="http://schemas.**xmlsoap.org/soap/envelope/<http://schemas.xmlsoap.org/soap/envelope/>
>> "><**soapenv:Body><soapenv:Fault><**faultcode>soapenv:Server</**
>> faultcode><faultstring>**unknown</faultstring><detail
>> /></soapenv:Fault></soapenv:**Body></soapenv:Envelope>
>>
>> I checked the Axis2 client side logs and they had following
>> lines suggesting 'Transport Sender Invoke Failed'
>>
>> [Fri Nov 11 03:15:57 2011] [debug] phase_resolver.c(139)
>> Service name is : __ANONYMOUS_SERVICE__
>> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(888)
>> Start:axis2_op_client_infer_**transport
>> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(954)
>> End:axis2_op_client_infer_**transport
>> [Fri Nov 11 03:15:57 2011] [debug]
>> http_transport_sender.c(246)
>> ctx_epr:http://192.168.75.109:**2800/MetaViewSimulator/**
>> services/ShService<http://192.168.75.109:2800/MetaViewSimulator/services/ShService>
>> [Fri Nov 11 03:15:57 2011] [debug]
>> http_transport_sender.c(805) using axis2 native http sender.
>> [Fri Nov 11 03:15:57 2011] [debug] http_sender.c(416)
>> msg_ctx_id:urn:uuid:8743b4cc-**0c56-1e11-3d80-0026b94edeb5
>> [Fri Nov 11 03:15:57 2011] [error] http_sender.c(1442) Error
>> occurred in transport
>> [Fri Nov 11 03:15:57 2011] [error] engine.c(179) Transport
>> sender invoke failed
>>
>> Thanks,
>>
>> Manoj Dhirde.
>>
>> On Fri, Nov 11, 2011 at 9:28 AM, Damitha Kumarage
>> <damitha@wso2.com <ma...@wso2.com>
>> <mailto:damitha@wso2.com <ma...@wso2.com>>> wrote:
>>
>> Hi Manoj,
>> Can you send the request and response messages to/from the
>> server
>> in both cases
>>
>> Thanks,
>> Damitha
>> Manoj Dhirde wrote:
>>
>> Hi Guys,
>>
>> We are putting together a C++ API for a WebService. We have
>> generated c-stubs from the wsdl for client and
>> generated the
>> server side code in Java. Now when we send request from our
>> API to the Java WebService we get following error,
>>
>> [Thu Nov 10 06:35:17 2011] [debug]
>> http_transport_sender.c(805) using axis2 native http
>> sender.
>> [Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
>> msg_ctx_id:urn:uuid:3586181c-**0ba9-1e11-3b20-0026b94edeb5
>> [Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442)
>> Error
>> occurred in transport
>> [Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport
>> sender invoke failed
>>
>> Then to check with python, we generated the server side
>> stubs
>> in python and started the Python WebService and it
>> processes
>> request successfully from the C++ API through same c stubs
>> client.
>> Not sure why its not working with Java WebService as our
>> preference is for Java for the Server side.
>>
>> Any help is greatly appreciated.
>>
>> Thanks,
>>
>> -- *Manoj Dhirde*
>> Senior Developer
>> *P:* 604-688-4332x808
>> *E:* mdhirde@incognito.com
>> <ma...@incognito.com> <mailto:mdhirde@incognito.com
>> <ma...@incognito.com>**>
>> <mailto:mdhirde@incognito.com
>> <ma...@incognito.com> <mailto:mdhirde@incognito.com
>> <ma...@incognito.com>**>>
>> *Toll-Free:* 1-800-877-1856
>> *F:* 604-688-4339
>> *VoIP:* sip:808@sip.incognito.com
>> <ma...@sip.incognito.com>
>> >
>> <ma...@sip.incognito.com>
>> <ma...@sip.incognito.com>
>> >>
>>
>> Incognito Software Inc. <http://www.incognito.com>
>> <http://www.incognito.com/**company/events<http://www.incognito.com/company/events>
>> >
>>
>>
>>
>>
>> -- ______________________________**
>> ______________________________**______
>>
>> Damitha Kumarage
>> Technical Lead; WSO2 Inc.
>> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>>
>> blog: " http://damithakumarage.**wordpress.com/<http://damithakumarage.wordpress.com/>
>> ______________________________**
>> ______________________________**______
>>
>> ------------------------------**
>> ------------------------------**---------
>> To unsubscribe, e-mail: c-user-unsubscribe@axis.**apache.org<c-...@axis.apache.org>
>> <ma...@axis.apache.org>
>> >
>> <ma...@axis.apache.org>
>> <ma...@axis.apache.org>
>> >>
>> For additional commands, e-mail:
>> c-user-help@axis.apache.org <ma...@axis.apache.org>
>> >
>> <ma...@axis.apache.org>
>> <ma...@axis.apache.org>
>> >>
>>
>>
>>
>>
>> -- *Manoj Dhirde*
>> Senior Developer
>> *P:* 604-688-4332x808
>> *E:* mdhirde@incognito.com <ma...@incognito.com>
>> <mailto:mdhirde@incognito.com <ma...@incognito.com>**>
>> *Toll-Free:* 1-800-877-1856
>>
>> *F:* 604-688-4339
>> *VoIP:* sip:808@sip.incognito.com
>> <ma...@sip.incognito.com>
>> >
>>
>> Incognito Software Inc. <http://www.incognito.com>
>> <http://www.incognito.com/**company/events<http://www.incognito.com/company/events>
>> >
>>
>>
>>
>>
>> -- ______________________________**______________________________*
>> *______
>>
>> Damitha Kumarage
>> Technical Lead; WSO2 Inc.
>> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>>
>> blog: " http://damithakumarage.**wordpress.com/<http://damithakumarage.wordpress.com/>
>> ______________________________**______________________________**______
>>
>> ------------------------------**------------------------------**
>> ---------
>> To unsubscribe, e-mail: c-user-unsubscribe@axis.**apache.org<c-...@axis.apache.org>
>> <ma...@axis.apache.org>
>> >
>> For additional commands, e-mail: c-user-help@axis.apache.org
>> <mailto:c-user-help@axis.**apache.org <c-...@axis.apache.org>>
>>
>>
>>
>>
>> --
>> *Manoj Dhirde*
>> Senior Developer
>> *P:* 604-688-4332x808
>> *E:* mdhirde@incognito.com <ma...@incognito.com>
>> *Toll-Free:* 1-800-877-1856
>>
>>
>> *F:* 604-688-4339
>> *VoIP:* sip:808@sip.incognito.com
>>
>> Incognito Software Inc. <http://www.incognito.com>
>>
>> <http://www.incognito.com/**company/events<http://www.incognito.com/company/events>
>> >
>>
>>
>>
>
> --
> ______________________________**______________________________**______
>
> Damitha Kumarage
> Technical Lead; WSO2 Inc.
> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>
> blog: " http://damithakumarage.**wordpress.com/<http://damithakumarage.wordpress.com/>
> ______________________________**______________________________**______
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.**apache.org<c-...@axis.apache.org>
> For additional commands, e-mail: c-user-help@axis.apache.org
>
>
--
*Manoj Dhirde*
Senior Developer
*P:* 604-688-4332x808
*E:* mdhirde@incognito.com
*Toll-Free:* 1-800-877-1856
*F:* 604-688-4339
*VoIP:* sip:808@sip.incognito.com
[image: Incognito Software Inc.] <http://www.incognito.com>
<http://www.incognito.com/company/events>
Re: Transport Sender Invoke Failed
Posted by Damitha Kumarage <da...@wso2.com>.
Hi Manoj,
Please note that the media type for SOAP 1.1 is |text/xml| and for SOAP
1.2 is |application/soap+xml|.
Also instead of SOAP 1.1 mandatory |SOAPAction| HTTP header, an optional
|action| parameter on the |application/soap+xml| media type
is introduced in SOAP 1.2.
Try changing those appropriately in your request.
Thanks,
Damitha
Manoj Dhirde wrote:
> Hi Damitha,
>
> Following are the contents of the header for each request,
>
> *C++ API talking to Python WebService through client built with
> c-stubs from the wsdl:*
>
> POST /services/ShService HTTP/1.1
> User-Agent: Axis2C/1.6.0
> SOAPAction: "http://www.metaswitch.com/ems/soap/sh/Sh/ShPull"
> Content-Length: 417
> Content-Type: text/xml;charset=UTF-8
> Host: 192.168.75.109:8081 <http://192.168.75.109:8081>
>
> *C++ API talking to Java WebService through client built with c-stubs
> from the wsdl:*
> *
> *
> POST /MetaSwitchSimulator/services/ShService HTTP/1.1
> User-Agent: Axis2C/1.6.0
> SOAPAction: "http://www.metaswitch.com/ems/soap/sh/Sh/ShPull"
> Content-Length: 417
> Content-Type: text/xml;charset=UTF-8
> Host: 192.168.75.109:2800 <http://192.168.75.109:2800>
>
> I will check the Server implementation again, the only change we added
> on top of the generated stubs in case both servers was to send back
> success response and nothing else was changed. But as suggested by
> you, I will double check the server implementation.
>
> I changed the SOAP version of client as well thinking that could have
> caused the issue with Java WebService, I changed it from 1.1 to 1.2
> but still same error.
>
> Thanks,
>
> Manoj Dhirde.
>
>
> On Fri, Nov 11, 2011 at 11:38 AM, Damitha Kumarage <damitha@wso2.com
> <ma...@wso2.com>> wrote:
>
> Hi Manoj,
> Server send back a soap fault where it does not give details of
> the problem that occured.
> Can you also send us the http headers of your request for both
> cases as well. Most probably this could be due to differences in
> the content type or
> action headers that the client send.
> Also double check your service implementation in java. The soap
> fault could also result due to an error thrown from your service.
>
> Thanks,
> Damitha
> Manoj Dhirde wrote:
>
> Hi Damitha,
>
> Thanks for looking into this.
>
> Following are the request/responses in case of a Python
> WebService and Java WebService, when a request was sent
> through a client built through c-stubs.
>
> *C++ API talking to Python WebService through client built
> with c-stubs from the wsdl:*
>
> *Request:*
> /<soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:sh="http://www.metaswitch.com/ems/soap/sh">/
> / <soapenv:Header/>/
> / <soapenv:Body>/
> / <sh:ShPull>/
> / <sh:UserIdentity>MySwitch/ABC
> Corporation</sh:UserIdentity>/
> / <sh:DataReference>0</sh:DataReference>/
> /
> <sh:ServiceIndication>Meta_BusinessGroup_CallPark</sh:ServiceIndication>/
> / <sh:OriginHost>mydomain.com?clientVersion=7.3
> <http://mydomain.com?clientVersion=7.3>
> <http://mydomain.com?clientVersion=7.3></sh:OriginHost>/
> / </sh:ShPull>/
> / </soapenv:Body>/
> / </soapenv:Envelope>/
> /
> /
> *Response:*
> HTTP/1.0 200 OK
> Server: ZSI/1.1 BaseHTTP/0.3 Python/2.5.2
> Date: Fri, 11 Nov 2011 03:12:54 GMT
> Content-type: text/xml; charset="utf-8"
> Content-Length: 878
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ZSI="http://www.zolera.com/schemas/ZSI/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <SOAP-ENV:Header></SOAP-ENV:Header>
> <SOAP-ENV:Body xmlns:ns1="http://www.metaswitch.com/ems/soap/sh">
> <ns1:ShPullResponse>
> <ns1:ResultCode>200</ns1:ResultCode>
> <ns1:ExtendedResult>
> <ns1:ExtendedResultCode>100</ns1:ExtendedResultCode>
>
> <ns1:ExtendedResultDetail>SUCCESS</ns1:ExtendedResultDetail>
> <ns1:ExtendedSubResults>
> <ns1:SubResult>
> <ns1:SubResultCode>100</ns1:SubResultCode>
>
> <ns1:SubResultDetail>SUCCESS</ns1:SubResultDetail>
>
> <ns1:SubResultSource>MetaSwitch.com</ns1:SubResultSource>
> </ns1:SubResult>
> </ns1:ExtendedSubResults></ns1:ExtendedResult>
> </ns1:ShPullResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> *C++ API talking to Java WebService through client built with
> c-stubs from the wsdl:*
> *
> *
> *Request:*
> *
> /<soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:sh="http://www.metaswitch.com/ems/soap/sh">/
> / <soapenv:Header/>/
> / <soapenv:Body>/
> / <sh:ShPull>/
> / <sh:UserIdentity>MySwitch/ABC
> Corporation</sh:UserIdentity>/
> / <sh:DataReference>0</sh:DataReference>/
> /
> <sh:ServiceIndication>Meta_BusinessGroup_CallPark</sh:ServiceIndication>/
> / <sh:OriginHost>mydomain.com?clientVersion=7.3
> <http://mydomain.com?clientVersion=7.3>
> <http://mydomain.com?clientVersion=7.3></sh:OriginHost>/
> / </sh:ShPull>/
> / </soapenv:Body>/
> / </soapenv:Envelope>/
> /
> /
> *
> *Response:*
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Fri, 11 Nov 2011 03:15:57 GMT
> Connection: close
>
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>unknown</faultstring><detail
> /></soapenv:Fault></soapenv:Body></soapenv:Envelope>
>
> I checked the Axis2 client side logs and they had following
> lines suggesting 'Transport Sender Invoke Failed'
>
> [Fri Nov 11 03:15:57 2011] [debug] phase_resolver.c(139)
> Service name is : __ANONYMOUS_SERVICE__
> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(888)
> Start:axis2_op_client_infer_transport
> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(954)
> End:axis2_op_client_infer_transport
> [Fri Nov 11 03:15:57 2011] [debug]
> http_transport_sender.c(246)
> ctx_epr:http://192.168.75.109:2800/MetaViewSimulator/services/ShService
> [Fri Nov 11 03:15:57 2011] [debug]
> http_transport_sender.c(805) using axis2 native http sender.
> [Fri Nov 11 03:15:57 2011] [debug] http_sender.c(416)
> msg_ctx_id:urn:uuid:8743b4cc-0c56-1e11-3d80-0026b94edeb5
> [Fri Nov 11 03:15:57 2011] [error] http_sender.c(1442) Error
> occurred in transport
> [Fri Nov 11 03:15:57 2011] [error] engine.c(179) Transport
> sender invoke failed
>
> Thanks,
>
> Manoj Dhirde.
>
> On Fri, Nov 11, 2011 at 9:28 AM, Damitha Kumarage
> <damitha@wso2.com <ma...@wso2.com>
> <mailto:damitha@wso2.com <ma...@wso2.com>>> wrote:
>
> Hi Manoj,
> Can you send the request and response messages to/from the
> server
> in both cases
>
> Thanks,
> Damitha
> Manoj Dhirde wrote:
>
> Hi Guys,
>
> We are putting together a C++ API for a WebService. We have
> generated c-stubs from the wsdl for client and
> generated the
> server side code in Java. Now when we send request from our
> API to the Java WebService we get following error,
>
> [Thu Nov 10 06:35:17 2011] [debug]
> http_transport_sender.c(805) using axis2 native http
> sender.
> [Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
> msg_ctx_id:urn:uuid:3586181c-0ba9-1e11-3b20-0026b94edeb5
> [Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442)
> Error
> occurred in transport
> [Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport
> sender invoke failed
>
> Then to check with python, we generated the server side
> stubs
> in python and started the Python WebService and it
> processes
> request successfully from the C++ API through same c stubs
> client.
> Not sure why its not working with Java WebService as our
> preference is for Java for the Server side.
>
> Any help is greatly appreciated.
>
> Thanks,
>
> -- *Manoj Dhirde*
> Senior Developer
> *P:* 604-688-4332x808
> *E:* mdhirde@incognito.com
> <ma...@incognito.com> <mailto:mdhirde@incognito.com
> <ma...@incognito.com>>
> <mailto:mdhirde@incognito.com
> <ma...@incognito.com> <mailto:mdhirde@incognito.com
> <ma...@incognito.com>>>
> *Toll-Free:* 1-800-877-1856
>
> *F:* 604-688-4339
> *VoIP:* sip:808@sip.incognito.com
> <ma...@sip.incognito.com>
> <mailto:sip%3A808@sip.incognito.com
> <ma...@sip.incognito.com>>
>
> Incognito Software Inc. <http://www.incognito.com>
> <http://www.incognito.com/company/events>
>
>
>
>
> --
> __________________________________________________________________
>
> Damitha Kumarage
> Technical Lead; WSO2 Inc.
> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>
> blog: " http://damithakumarage.wordpress.com/
>
> __________________________________________________________________
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> <ma...@axis.apache.org>
> <mailto:c-user-unsubscribe@axis.apache.org
> <ma...@axis.apache.org>>
> For additional commands, e-mail:
> c-user-help@axis.apache.org <ma...@axis.apache.org>
> <mailto:c-user-help@axis.apache.org
> <ma...@axis.apache.org>>
>
>
>
>
> --
> *Manoj Dhirde*
> Senior Developer
> *P:* 604-688-4332x808
> *E:* mdhirde@incognito.com <ma...@incognito.com>
> <mailto:mdhirde@incognito.com <ma...@incognito.com>>
> *Toll-Free:* 1-800-877-1856
>
>
> *F:* 604-688-4339
> *VoIP:* sip:808@sip.incognito.com
> <ma...@sip.incognito.com>
>
> Incognito Software Inc. <http://www.incognito.com>
>
> <http://www.incognito.com/company/events>
>
>
>
>
> --
> __________________________________________________________________
>
> Damitha Kumarage
> Technical Lead; WSO2 Inc.
> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>
> blog: " http://damithakumarage.wordpress.com/
> __________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> <ma...@axis.apache.org>
> For additional commands, e-mail: c-user-help@axis.apache.org
> <ma...@axis.apache.org>
>
>
>
>
> --
> *Manoj Dhirde*
> Senior Developer
> *P:* 604-688-4332x808
> *E:* mdhirde@incognito.com <ma...@incognito.com>
> *Toll-Free:* 1-800-877-1856
>
>
> *F:* 604-688-4339
> *VoIP:* sip:808@sip.incognito.com
>
> Incognito Software Inc. <http://www.incognito.com>
>
> <http://www.incognito.com/company/events>
>
>
--
__________________________________________________________________
Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/
blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org
Re: Transport Sender Invoke Failed
Posted by Manoj Dhirde <md...@incognito.com>.
Hi Damitha,
Following are the contents of the header for each request,
*C++ API talking to Python WebService through client built with c-stubs
from the wsdl:*
POST /services/ShService HTTP/1.1
User-Agent: Axis2C/1.6.0
SOAPAction: "http://www.metaswitch.com/ems/soap/sh/Sh/ShPull"
Content-Length: 417
Content-Type: text/xml;charset=UTF-8
Host: 192.168.75.109:8081
*C++ API talking to Java WebService through client built with c-stubs from
the wsdl:*
*
*
POST /MetaSwitchSimulator/services/ShService HTTP/1.1
User-Agent: Axis2C/1.6.0
SOAPAction: "http://www.metaswitch.com/ems/soap/sh/Sh/ShPull"
Content-Length: 417
Content-Type: text/xml;charset=UTF-8
Host: 192.168.75.109:2800
I will check the Server implementation again, the only change we added on
top of the generated stubs in case both servers was to send back success
response and nothing else was changed. But as suggested by you, I will
double check the server implementation.
I changed the SOAP version of client as well thinking that could have
caused the issue with Java WebService, I changed it from 1.1 to 1.2 but
still same error.
Thanks,
Manoj Dhirde.
On Fri, Nov 11, 2011 at 11:38 AM, Damitha Kumarage <da...@wso2.com> wrote:
> Hi Manoj,
> Server send back a soap fault where it does not give details of the
> problem that occured.
> Can you also send us the http headers of your request for both cases as
> well. Most probably this could be due to differences in the content type or
> action headers that the client send.
> Also double check your service implementation in java. The soap fault
> could also result due to an error thrown from your service.
>
> Thanks,
> Damitha
> Manoj Dhirde wrote:
>
>> Hi Damitha,
>>
>> Thanks for looking into this.
>>
>> Following are the request/responses in case of a Python WebService and
>> Java WebService, when a request was sent through a client built through
>> c-stubs.
>>
>> *C++ API talking to Python WebService through client built with c-stubs
>> from the wsdl:*
>>
>> *Request:*
>> /<soapenv:Envelope xmlns:soapenv="http://schemas.**
>> xmlsoap.org/soap/envelope/ <http://schemas.xmlsoap.org/soap/envelope/>"
>> xmlns:sh="http://www.**metaswitch.com/ems/soap/sh<http://www.metaswitch.com/ems/soap/sh>
>> ">/
>> / <soapenv:Header/>/
>> / <soapenv:Body>/
>> / <sh:ShPull>/
>> / <sh:UserIdentity>MySwitch/ABC Corporation</sh:UserIdentity>/
>> / <sh:DataReference>0</sh:**DataReference>/
>> / <sh:ServiceIndication>Meta_**BusinessGroup_CallPark</sh:**
>> ServiceIndication>/
>> / <sh:OriginHost>mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3><
>> http://mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> ></sh:**OriginHost>/
>> / </sh:ShPull>/
>> / </soapenv:Body>/
>> / </soapenv:Envelope>/
>> /
>> /
>> *Response:*
>> HTTP/1.0 200 OK
>> Server: ZSI/1.1 BaseHTTP/0.3 Python/2.5.2
>> Date: Fri, 11 Nov 2011 03:12:54 GMT
>> Content-type: text/xml; charset="utf-8"
>> Content-Length: 878
>>
>> <SOAP-ENV:Envelope xmlns:SOAP-ENC="http://**schemas.xmlsoap.org/soap/**
>> encoding/ <http://schemas.xmlsoap.org/soap/encoding/>" xmlns:SOAP-ENV="
>> http://**schemas.xmlsoap.org/soap/**envelope/<http://schemas.xmlsoap.org/soap/envelope/>"
>> xmlns:ZSI="http://www.zolera.**com/schemas/ZSI/<http://www.zolera.com/schemas/ZSI/>"
>> xmlns:xsd="http://www.w3.org/**2001/XMLSchema<http://www.w3.org/2001/XMLSchema>"
>> xmlns:xsi="http://www.w3.org/**2001/XMLSchema-instance<http://www.w3.org/2001/XMLSchema-instance>
>> ">
>> <SOAP-ENV:Header></SOAP-ENV:**Header>
>> <SOAP-ENV:Body xmlns:ns1="http://www.**metaswitch.com/ems/soap/sh<http://www.metaswitch.com/ems/soap/sh>
>> ">
>> <ns1:ShPullResponse>
>> <ns1:ResultCode>200</ns1:**ResultCode>
>> <ns1:ExtendedResult>
>> <ns1:ExtendedResultCode>100</**ns1:ExtendedResultCode>
>> <ns1:ExtendedResultDetail>**SUCCESS</ns1:**
>> ExtendedResultDetail>
>> <ns1:ExtendedSubResults>
>> <ns1:SubResult>
>> <ns1:SubResultCode>100</ns1:**SubResultCode>
>> <ns1:SubResultDetail>SUCCESS</**
>> ns1:SubResultDetail>
>> <ns1:SubResultSource>**MetaSwitch.com</ns1:**
>> SubResultSource>
>> </ns1:SubResult>
>> </ns1:ExtendedSubResults></**ns1:ExtendedResult>
>> </ns1:ShPullResponse>
>> </SOAP-ENV:Body>
>> </SOAP-ENV:Envelope>
>>
>> *C++ API talking to Java WebService through client built with c-stubs
>> from the wsdl:*
>> *
>> *
>> *Request:*
>> *
>> /<soapenv:Envelope xmlns:soapenv="http://schemas.**
>> xmlsoap.org/soap/envelope/ <http://schemas.xmlsoap.org/soap/envelope/>"
>> xmlns:sh="http://www.**metaswitch.com/ems/soap/sh<http://www.metaswitch.com/ems/soap/sh>
>> ">/
>> / <soapenv:Header/>/
>> / <soapenv:Body>/
>> / <sh:ShPull>/
>> / <sh:UserIdentity>MySwitch/ABC Corporation</sh:UserIdentity>/
>> / <sh:DataReference>0</sh:**DataReference>/
>> / <sh:ServiceIndication>Meta_**BusinessGroup_CallPark</sh:**
>> ServiceIndication>/
>> / <sh:OriginHost>mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3><
>> http://mydomain.com?**clientVersion=7.3<http://mydomain.com?clientVersion=7.3>
>> ></sh:**OriginHost>/
>> / </sh:ShPull>/
>> / </soapenv:Body>/
>> / </soapenv:Envelope>/
>> /
>> /
>> *
>> *Response:*
>> HTTP/1.1 500 Internal Server Error
>> Server: Apache-Coyote/1.1
>> Content-Type: text/xml;charset=UTF-8
>> Transfer-Encoding: chunked
>> Date: Fri, 11 Nov 2011 03:15:57 GMT
>> Connection: close
>>
>> <?xml version='1.0' encoding='UTF-8'?><soapenv:**Envelope xmlns:soapenv="
>> http://schemas.**xmlsoap.org/soap/envelope/<http://schemas.xmlsoap.org/soap/envelope/>
>> "><**soapenv:Body><soapenv:Fault><**faultcode>soapenv:Server</**
>> faultcode><faultstring>**unknown</faultstring><detail
>> /></soapenv:Fault></soapenv:**Body></soapenv:Envelope>
>>
>> I checked the Axis2 client side logs and they had following lines
>> suggesting 'Transport Sender Invoke Failed'
>>
>> [Fri Nov 11 03:15:57 2011] [debug] phase_resolver.c(139) Service name is
>> : __ANONYMOUS_SERVICE__
>> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(888)
>> Start:axis2_op_client_infer_**transport
>> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(954)
>> End:axis2_op_client_infer_**transport
>> [Fri Nov 11 03:15:57 2011] [debug] http_transport_sender.c(246) ctx_epr:
>> http://192.168.75.109:**2800/MetaViewSimulator/**services/ShService<http://192.168.75.109:2800/MetaViewSimulator/services/ShService>
>> [Fri Nov 11 03:15:57 2011] [debug] http_transport_sender.c(805) using
>> axis2 native http sender.
>> [Fri Nov 11 03:15:57 2011] [debug] http_sender.c(416)
>> msg_ctx_id:urn:uuid:8743b4cc-**0c56-1e11-3d80-0026b94edeb5
>> [Fri Nov 11 03:15:57 2011] [error] http_sender.c(1442) Error occurred in
>> transport
>> [Fri Nov 11 03:15:57 2011] [error] engine.c(179) Transport sender invoke
>> failed
>>
>> Thanks,
>>
>> Manoj Dhirde.
>>
>> On Fri, Nov 11, 2011 at 9:28 AM, Damitha Kumarage <damitha@wso2.com<mailto:
>> damitha@wso2.com>> wrote:
>>
>> Hi Manoj,
>> Can you send the request and response messages to/from the server
>> in both cases
>>
>> Thanks,
>> Damitha
>> Manoj Dhirde wrote:
>>
>> Hi Guys,
>>
>> We are putting together a C++ API for a WebService. We have
>> generated c-stubs from the wsdl for client and generated the
>> server side code in Java. Now when we send request from our
>> API to the Java WebService we get following error,
>>
>> [Thu Nov 10 06:35:17 2011] [debug]
>> http_transport_sender.c(805) using axis2 native http sender.
>> [Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
>> msg_ctx_id:urn:uuid:3586181c-**0ba9-1e11-3b20-0026b94edeb5
>> [Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442) Error
>> occurred in transport
>> [Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport
>> sender invoke failed
>>
>> Then to check with python, we generated the server side stubs
>> in python and started the Python WebService and it processes
>> request successfully from the C++ API through same c stubs
>> client.
>> Not sure why its not working with Java WebService as our
>> preference is for Java for the Server side.
>>
>> Any help is greatly appreciated.
>>
>> Thanks,
>>
>> -- *Manoj Dhirde*
>> Senior Developer
>> *P:* 604-688-4332x808
>> *E:* mdhirde@incognito.com <ma...@incognito.com>
>> <mailto:mdhirde@incognito.com <ma...@incognito.com>**>
>> *Toll-Free:* 1-800-877-1856
>>
>> *F:* 604-688-4339
>> *VoIP:* sip:808@sip.incognito.com
>> <ma...@sip.incognito.com>
>> >
>>
>> Incognito Software Inc. <http://www.incognito.com>
>> <http://www.incognito.com/**company/events<http://www.incognito.com/company/events>
>> >
>>
>>
>>
>>
>> -- ______________________________**______________________________*
>> *______
>>
>> Damitha Kumarage
>> Technical Lead; WSO2 Inc.
>> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>>
>> blog: " http://damithakumarage.**wordpress.com/<http://damithakumarage.wordpress.com/>
>> ______________________________**______________________________**______
>>
>> ------------------------------**------------------------------**
>> ---------
>> To unsubscribe, e-mail: c-user-unsubscribe@axis.**apache.org<c-...@axis.apache.org>
>> <ma...@axis.apache.org>
>> >
>> For additional commands, e-mail: c-user-help@axis.apache.org
>> <mailto:c-user-help@axis.**apache.org <c-...@axis.apache.org>>
>>
>>
>>
>>
>> --
>> *Manoj Dhirde*
>> Senior Developer
>> *P:* 604-688-4332x808
>> *E:* mdhirde@incognito.com <ma...@incognito.com>
>> *Toll-Free:* 1-800-877-1856
>>
>>
>> *F:* 604-688-4339
>> *VoIP:* sip:808@sip.incognito.com
>>
>> Incognito Software Inc. <http://www.incognito.com>
>>
>> <http://www.incognito.com/**company/events<http://www.incognito.com/company/events>
>> >
>>
>>
>>
>
> --
> ______________________________**______________________________**______
>
> Damitha Kumarage
> Technical Lead; WSO2 Inc.
> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>
> blog: " http://damithakumarage.**wordpress.com/<http://damithakumarage.wordpress.com/>
> ______________________________**______________________________**______
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.**apache.org<c-...@axis.apache.org>
> For additional commands, e-mail: c-user-help@axis.apache.org
>
>
--
*Manoj Dhirde*
Senior Developer
*P:* 604-688-4332x808
*E:* mdhirde@incognito.com
*Toll-Free:* 1-800-877-1856
*F:* 604-688-4339
*VoIP:* sip:808@sip.incognito.com
[image: Incognito Software Inc.] <http://www.incognito.com>
<http://www.incognito.com/company/events>
Re: Transport Sender Invoke Failed
Posted by Damitha Kumarage <da...@wso2.com>.
Hi Manoj,
Server send back a soap fault where it does not give details of the
problem that occured.
Can you also send us the http headers of your request for both cases as
well. Most probably this could be due to differences in the content type or
action headers that the client send.
Also double check your service implementation in java. The soap fault
could also result due to an error thrown from your service.
Thanks,
Damitha
Manoj Dhirde wrote:
> Hi Damitha,
>
> Thanks for looking into this.
>
> Following are the request/responses in case of a Python WebService and
> Java WebService, when a request was sent through a client built
> through c-stubs.
>
> *C++ API talking to Python WebService through client built with
> c-stubs from the wsdl:*
>
> *Request:*
> /<soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:sh="http://www.metaswitch.com/ems/soap/sh">/
> / <soapenv:Header/>/
> / <soapenv:Body>/
> / <sh:ShPull>/
> / <sh:UserIdentity>MySwitch/ABC Corporation</sh:UserIdentity>/
> / <sh:DataReference>0</sh:DataReference>/
> /
> <sh:ServiceIndication>Meta_BusinessGroup_CallPark</sh:ServiceIndication>/
> / <sh:OriginHost>mydomain.com?clientVersion=7.3
> <http://mydomain.com?clientVersion=7.3></sh:OriginHost>/
> / </sh:ShPull>/
> / </soapenv:Body>/
> / </soapenv:Envelope>/
> /
> /
> *Response:*
> HTTP/1.0 200 OK
> Server: ZSI/1.1 BaseHTTP/0.3 Python/2.5.2
> Date: Fri, 11 Nov 2011 03:12:54 GMT
> Content-type: text/xml; charset="utf-8"
> Content-Length: 878
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ZSI="http://www.zolera.com/schemas/ZSI/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <SOAP-ENV:Header></SOAP-ENV:Header>
> <SOAP-ENV:Body xmlns:ns1="http://www.metaswitch.com/ems/soap/sh">
> <ns1:ShPullResponse>
> <ns1:ResultCode>200</ns1:ResultCode>
> <ns1:ExtendedResult>
> <ns1:ExtendedResultCode>100</ns1:ExtendedResultCode>
> <ns1:ExtendedResultDetail>SUCCESS</ns1:ExtendedResultDetail>
> <ns1:ExtendedSubResults>
> <ns1:SubResult>
> <ns1:SubResultCode>100</ns1:SubResultCode>
> <ns1:SubResultDetail>SUCCESS</ns1:SubResultDetail>
>
> <ns1:SubResultSource>MetaSwitch.com</ns1:SubResultSource>
> </ns1:SubResult>
> </ns1:ExtendedSubResults></ns1:ExtendedResult>
> </ns1:ShPullResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> *C++ API talking to Java WebService through client built with c-stubs
> from the wsdl:*
> *
> *
> *Request:*
> *
> /<soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:sh="http://www.metaswitch.com/ems/soap/sh">/
> / <soapenv:Header/>/
> / <soapenv:Body>/
> / <sh:ShPull>/
> / <sh:UserIdentity>MySwitch/ABC Corporation</sh:UserIdentity>/
> / <sh:DataReference>0</sh:DataReference>/
> /
> <sh:ServiceIndication>Meta_BusinessGroup_CallPark</sh:ServiceIndication>/
> / <sh:OriginHost>mydomain.com?clientVersion=7.3
> <http://mydomain.com?clientVersion=7.3></sh:OriginHost>/
> / </sh:ShPull>/
> / </soapenv:Body>/
> / </soapenv:Envelope>/
> /
> /
> *
> *Response:*
> HTTP/1.1 500 Internal Server Error
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Date: Fri, 11 Nov 2011 03:15:57 GMT
> Connection: close
>
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>unknown</faultstring><detail
> /></soapenv:Fault></soapenv:Body></soapenv:Envelope>
>
> I checked the Axis2 client side logs and they had following lines
> suggesting 'Transport Sender Invoke Failed'
>
> [Fri Nov 11 03:15:57 2011] [debug] phase_resolver.c(139) Service name
> is : __ANONYMOUS_SERVICE__
> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(888)
> Start:axis2_op_client_infer_transport
> [Fri Nov 11 03:15:57 2011] [debug] op_client.c(954)
> End:axis2_op_client_infer_transport
> [Fri Nov 11 03:15:57 2011] [debug] http_transport_sender.c(246)
> ctx_epr:http://192.168.75.109:2800/MetaViewSimulator/services/ShService
> [Fri Nov 11 03:15:57 2011] [debug] http_transport_sender.c(805) using
> axis2 native http sender.
> [Fri Nov 11 03:15:57 2011] [debug] http_sender.c(416)
> msg_ctx_id:urn:uuid:8743b4cc-0c56-1e11-3d80-0026b94edeb5
> [Fri Nov 11 03:15:57 2011] [error] http_sender.c(1442) Error occurred
> in transport
> [Fri Nov 11 03:15:57 2011] [error] engine.c(179) Transport sender
> invoke failed
>
> Thanks,
>
> Manoj Dhirde.
>
> On Fri, Nov 11, 2011 at 9:28 AM, Damitha Kumarage <damitha@wso2.com
> <ma...@wso2.com>> wrote:
>
> Hi Manoj,
> Can you send the request and response messages to/from the server
> in both cases
>
> Thanks,
> Damitha
> Manoj Dhirde wrote:
>
> Hi Guys,
>
> We are putting together a C++ API for a WebService. We have
> generated c-stubs from the wsdl for client and generated the
> server side code in Java. Now when we send request from our
> API to the Java WebService we get following error,
>
> [Thu Nov 10 06:35:17 2011] [debug]
> http_transport_sender.c(805) using axis2 native http sender.
> [Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
> msg_ctx_id:urn:uuid:3586181c-0ba9-1e11-3b20-0026b94edeb5
> [Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442) Error
> occurred in transport
> [Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport
> sender invoke failed
>
> Then to check with python, we generated the server side stubs
> in python and started the Python WebService and it processes
> request successfully from the C++ API through same c stubs
> client.
> Not sure why its not working with Java WebService as our
> preference is for Java for the Server side.
>
> Any help is greatly appreciated.
>
> Thanks,
>
> --
> *Manoj Dhirde*
> Senior Developer
> *P:* 604-688-4332x808
> *E:* mdhirde@incognito.com <ma...@incognito.com>
> <mailto:mdhirde@incognito.com <ma...@incognito.com>>
> *Toll-Free:* 1-800-877-1856
>
>
> *F:* 604-688-4339
> *VoIP:* sip:808@sip.incognito.com
> <ma...@sip.incognito.com>
>
> Incognito Software Inc. <http://www.incognito.com>
>
> <http://www.incognito.com/company/events>
>
>
>
>
> --
> __________________________________________________________________
>
> Damitha Kumarage
> Technical Lead; WSO2 Inc.
> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>
> blog: " http://damithakumarage.wordpress.com/
> __________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
> <ma...@axis.apache.org>
> For additional commands, e-mail: c-user-help@axis.apache.org
> <ma...@axis.apache.org>
>
>
>
>
> --
> *Manoj Dhirde*
> Senior Developer
> *P:* 604-688-4332x808
> *E:* mdhirde@incognito.com <ma...@incognito.com>
> *Toll-Free:* 1-800-877-1856
>
>
> *F:* 604-688-4339
> *VoIP:* sip:808@sip.incognito.com
>
> Incognito Software Inc. <http://www.incognito.com>
>
> <http://www.incognito.com/company/events>
>
>
--
__________________________________________________________________
Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/
blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org
Re: Transport Sender Invoke Failed
Posted by Manoj Dhirde <md...@incognito.com>.
Hi Damitha,
Thanks for looking into this.
Following are the request/responses in case of a Python WebService and Java
WebService, when a request was sent through a client built through c-stubs.
*C++ API talking to Python WebService through client built with c-stubs
from the wsdl:*
*Request:*
*<soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:sh="
http://www.metaswitch.com/ems/soap/sh">*
* <soapenv:Header/>*
* <soapenv:Body>*
* <sh:ShPull>*
* <sh:UserIdentity>MySwitch/ABC Corporation</sh:UserIdentity>*
* <sh:DataReference>0</sh:DataReference>*
*
<sh:ServiceIndication>Meta_BusinessGroup_CallPark</sh:ServiceIndication>*
* <sh:OriginHost>mydomain.com?clientVersion=7.3</sh:OriginHost>*
* </sh:ShPull>*
* </soapenv:Body>*
* </soapenv:Envelope>*
*
*
*Response:*
HTTP/1.0 200 OK
Server: ZSI/1.1 BaseHTTP/0.3 Python/2.5.2
Date: Fri, 11 Nov 2011 03:12:54 GMT
Content-type: text/xml; charset="utf-8"
Content-Length: 878
<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ZSI="
http://www.zolera.com/schemas/ZSI/" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Header></SOAP-ENV:Header>
<SOAP-ENV:Body xmlns:ns1="http://www.metaswitch.com/ems/soap/sh">
<ns1:ShPullResponse>
<ns1:ResultCode>200</ns1:ResultCode>
<ns1:ExtendedResult>
<ns1:ExtendedResultCode>100</ns1:ExtendedResultCode>
<ns1:ExtendedResultDetail>SUCCESS</ns1:ExtendedResultDetail>
<ns1:ExtendedSubResults>
<ns1:SubResult>
<ns1:SubResultCode>100</ns1:SubResultCode>
<ns1:SubResultDetail>SUCCESS</ns1:SubResultDetail>
<ns1:SubResultSource>MetaSwitch.com</ns1:SubResultSource>
</ns1:SubResult>
</ns1:ExtendedSubResults></ns1:ExtendedResult>
</ns1:ShPullResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
*C++ API talking to Java WebService through client built with c-stubs from
the wsdl:*
*
*
*Request:*
*
<soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:sh="
http://www.metaswitch.com/ems/soap/sh">
<soapenv:Header/>
<soapenv:Body>
<sh:ShPull>
<sh:UserIdentity>MySwitch/ABC Corporation</sh:UserIdentity>
<sh:DataReference>0</sh:DataReference>
<sh:ServiceIndication>Meta_BusinessGroup_CallPark</sh:ServiceIndication>
<sh:OriginHost>mydomain.com?clientVersion=7.3</sh:OriginHost>
</sh:ShPull>
</soapenv:Body>
</soapenv:Envelope>
*
*Response:*
HTTP/1.1 500 Internal Server Error
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Fri, 11 Nov 2011 03:15:57 GMT
Connection: close
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>unknown</faultstring><detail
/></soapenv:Fault></soapenv:Body></soapenv:Envelope>
I checked the Axis2 client side logs and they had following lines
suggesting 'Transport Sender Invoke Failed'
[Fri Nov 11 03:15:57 2011] [debug] phase_resolver.c(139) Service name is :
__ANONYMOUS_SERVICE__
[Fri Nov 11 03:15:57 2011] [debug] op_client.c(888)
Start:axis2_op_client_infer_transport
[Fri Nov 11 03:15:57 2011] [debug] op_client.c(954)
End:axis2_op_client_infer_transport
[Fri Nov 11 03:15:57 2011] [debug] http_transport_sender.c(246) ctx_epr:
http://192.168.75.109:2800/MetaViewSimulator/services/ShService
[Fri Nov 11 03:15:57 2011] [debug] http_transport_sender.c(805) using axis2
native http sender.
[Fri Nov 11 03:15:57 2011] [debug] http_sender.c(416)
msg_ctx_id:urn:uuid:8743b4cc-0c56-1e11-3d80-0026b94edeb5
[Fri Nov 11 03:15:57 2011] [error] http_sender.c(1442) Error occurred in
transport
[Fri Nov 11 03:15:57 2011] [error] engine.c(179) Transport sender invoke
failed
Thanks,
Manoj Dhirde.
On Fri, Nov 11, 2011 at 9:28 AM, Damitha Kumarage <da...@wso2.com> wrote:
> Hi Manoj,
> Can you send the request and response messages to/from the server in both
> cases
>
> Thanks,
> Damitha
> Manoj Dhirde wrote:
>
>> Hi Guys,
>>
>> We are putting together a C++ API for a WebService. We have generated
>> c-stubs from the wsdl for client and generated the server side code in
>> Java. Now when we send request from our API to the Java WebService we get
>> following error,
>>
>> [Thu Nov 10 06:35:17 2011] [debug] http_transport_sender.c(805) using
>> axis2 native http sender.
>> [Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
>> msg_ctx_id:urn:uuid:3586181c-**0ba9-1e11-3b20-0026b94edeb5
>> [Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442) Error occurred in
>> transport
>> [Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport sender invoke
>> failed
>>
>> Then to check with python, we generated the server side stubs in python
>> and started the Python WebService and it processes request successfully
>> from the C++ API through same c stubs client.
>> Not sure why its not working with Java WebService as our preference is
>> for Java for the Server side.
>>
>> Any help is greatly appreciated.
>>
>> Thanks,
>>
>> --
>> *Manoj Dhirde*
>> Senior Developer
>> *P:* 604-688-4332x808
>> *E:* mdhirde@incognito.com <ma...@incognito.com>
>> *Toll-Free:* 1-800-877-1856
>>
>>
>> *F:* 604-688-4339
>> *VoIP:* sip:808@sip.incognito.com
>>
>> Incognito Software Inc. <http://www.incognito.com>
>>
>> <http://www.incognito.com/**company/events<http://www.incognito.com/company/events>
>> >
>>
>>
>>
>
> --
> ______________________________**______________________________**______
>
> Damitha Kumarage
> Technical Lead; WSO2 Inc.
> "Oxygenating the Web Service Platform; " http://www.wso2.com/
>
> blog: " http://damithakumarage.**wordpress.com/<http://damithakumarage.wordpress.com/>
> ______________________________**______________________________**______
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: c-user-unsubscribe@axis.**apache.org<c-...@axis.apache.org>
> For additional commands, e-mail: c-user-help@axis.apache.org
>
>
--
*Manoj Dhirde*
Senior Developer
*P:* 604-688-4332x808
*E:* mdhirde@incognito.com
*Toll-Free:* 1-800-877-1856
*F:* 604-688-4339
*VoIP:* sip:808@sip.incognito.com
[image: Incognito Software Inc.] <http://www.incognito.com>
<http://www.incognito.com/company/events>
Re: Transport Sender Invoke Failed
Posted by Damitha Kumarage <da...@wso2.com>.
Hi Manoj,
Can you send the request and response messages to/from the server in
both cases
Thanks,
Damitha
Manoj Dhirde wrote:
> Hi Guys,
>
> We are putting together a C++ API for a WebService. We have generated
> c-stubs from the wsdl for client and generated the server side code in
> Java. Now when we send request from our API to the Java WebService we
> get following error,
>
> [Thu Nov 10 06:35:17 2011] [debug] http_transport_sender.c(805) using
> axis2 native http sender.
> [Thu Nov 10 06:35:17 2011] [debug] http_sender.c(416)
> msg_ctx_id:urn:uuid:3586181c-0ba9-1e11-3b20-0026b94edeb5
> [Thu Nov 10 06:35:17 2011] [error] http_sender.c(1442) Error occurred
> in transport
> [Thu Nov 10 06:35:17 2011] [error] engine.c(179) Transport sender
> invoke failed
>
> Then to check with python, we generated the server side stubs in
> python and started the Python WebService and it processes request
> successfully from the C++ API through same c stubs client.
>
> Not sure why its not working with Java WebService as our preference is
> for Java for the Server side.
>
> Any help is greatly appreciated.
>
> Thanks,
>
> --
> *Manoj Dhirde*
> Senior Developer
> *P:* 604-688-4332x808
> *E:* mdhirde@incognito.com <ma...@incognito.com>
> *Toll-Free:* 1-800-877-1856
>
>
> *F:* 604-688-4339
> *VoIP:* sip:808@sip.incognito.com
>
> Incognito Software Inc. <http://www.incognito.com>
>
> <http://www.incognito.com/company/events>
>
>
--
__________________________________________________________________
Damitha Kumarage
Technical Lead; WSO2 Inc.
"Oxygenating the Web Service Platform; " http://www.wso2.com/
blog: " http://damithakumarage.wordpress.com/
__________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org