Re: duplicate calls to web service

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Kim,

Is ':::xml document:::' exactly 2354 bytes long?  (I can't check since 
you didn't post the actual document.)

Assuming that it is, I don't see anything wrong here.   You say that 
other folks have told you it can take 'several minutes', but you have 
the timeout set to 180 (3 minutes).   Have you tried a higher value, 
such as 600 (10 minutes)?




On 2/14/2011 11:52 AM, Kim Gibson wrote:
> Thank you Scott, I thought I had was returning to the calling program if
> the http_url_post_xml() returned an error, but obviously was not. Bah!
>
> I'm still not receiving a response, and am eventually timing out, even
> after setting the timeout to 180 seconds. The debug file follows:
>
> =============================
> HTTPAPI Ver 1.24beta11 released 2010-09-09
> OS/400 Ver V6R1M0
>
> http_persist_open(): entered
> http_long_ParseURL(): entered
> DNS resolver retrans: 2
> DNS resolver retry  : 2
> DNS resolver options: x'00000136'
> DNS default domain: companyiworkfor.com
> DNS server found: 192.168.30.9
> DNS server found: 207.170.210.162
> DNS server found: 168.215.210.50
> ------------------------------------------------------------------------
> -------------
> Dump of server-side certificate information:
> ------------------------------------------------------------------------
> -------------
> Cert Validation Code = 0
> -----BEGIN CERTIFICATE-----
> :::certificate  information:::
> -----END CERTIFICATE-----
> Serial Number: 03:C3:ED:21:80:79:0E:5B:8D:1B:42:91:12:2C:B6:79
> Common Name: ws.labone.com
> Country: US
> State/Province: New Jersey
> Locality: Teterboro
> Org Unit: Quest Diagnostics, Incorporated
> Org: Corp IT - renwws01
> Issuer Org: VeriSign Trust Network
> Issuer Org Unit: www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97
> VeriSign, OU=VeriSign International Server CA - Class 3, OU=VeriSign,
> Inc.
> Version: 03
> not before: 20101005180000
> not after: 20111006175959
> pub key alg: 1.2.840.113549.1.1.5
>
> Protocol Used: TLS Version 1
> http_persist_post(): entered
> http_long_ParseURL(): entered
> do_oper(POST): entered
> POST /services/eoservice.asmx HTTP/1.1
> Host: ws.labone.com
> User-Agent: http-api/1.24
> Content-Type: text/xml
> Content-Length: 2354
>
>
> senddoc(): entered
>
> :::xml document:::
>
> recvresp(): entered
> SetError() #43: CommSSL_Read:  time-out!
> recvresp(): end with timeout
> http_close(): entered
>
> ==================================
>
> Our Underwriting department can run this process themselves from a web
> browser, and they tell me that it can take several minutes to receive a
> result. I'm going to call the web services tech support people to make
> sure they're receiving my requests. Thanks so much for your help, Scott.
>
> Kim Gibson
>
>
>> Hi Kim,
>
>> HTTP consists of two parts:
>> 1) Send Request.
>> 2) Receive Response.
>
>> Your logs show that you are successfully doing sending the request, but
>
>> you are not receiving a response.  HTTPAPI is trying to receive it, but
>
>> it's receiving nothing from the server, and eventually timing out.
>
>> That means that neither your StartOfElement() nor your EndOfElement()
>> handler is being called.  I'm not sure where 'embfile' is coming from,
>> but my guess would be that you're creating it in the EndOfElement()
>> routine.  So if that routine is never called, 'embfile' won't exist.>
>
>> Your program does not end when http_url_post_xml() returns an error...
>> it keeps going, and calls http_parse_xml_stmf().  When that routine is
>> called, there is no embfile, so it returns 'No such path or directory.'
>
>>   (as it should.)
>
>> You need to find out why the server isn't sending you a response!  Why
>> is it timing out?
>
>> also, one suggestion for you:   if http_url_post_xml() fails, you might
>
>> want to abort the rest of the routine.  After all, if it failed, you
>> didn't get an XML file.  Why proceed to try to parse it?
>
>
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------