[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: duplicate calls to web service



Hi Scott,

I've got a call in to the web services tech support people to see if we
can track down the issue with the response. Apparently when they receive
a request, they generate a report of prescription data that is available
to our Underwriting department on the web service company's internet
site. Even when my requests with a 10-minute timeout do not get a
response, the prescription data report is generated. So obviously they
are receiving my requests. 

I'm sure that it's nothing to do with HTTPAPI, but I really appreciate
your help and feedback in tracking these problems down. I've started
creating a separate debug file for each request so I can see exactly
what goes on. Sometimes the response is received, sometimes it isn't.
Hopefully the tech support people will call me soon & we can get this
resolved.

HTTPAPI has been invaluable to me. I'm an RPGILE/CLLE novice (duh) who
loves the iSeries, and being able to consume web services from the
iSeries so easily is way, way cool. Thanks!

Kim


* From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
* To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
* Subject: Re: duplicate calls to web service
* Date: Mon, 14 Feb 2011 15:53:52 -0600
________________________________________
>>On 2/14/2011 2:53 PM, Kim Gibson wrote:
>> It sounds as if I may have to figure out a way to resubmit the failed
>> requests at another time of day, in the hopes of getting a response.

>The "resubmit" might be where you're ending up with duplicates.  and 
>that's a problem!  IMHO, the server should be using something like 
>commitment control.  It should wait until it's able to successfully
send 
>you a '200' response, and response XML document, without any errors 
>before it actually commits the transaction.  If it fails to send you 
>this response, it should roll back the transaction.

>But it sounds like it's recording the transaction (and committing it) 
>and when that is successful, it's sending your response.  Problem is, 
>for some reason, it's failing to send that response.  So you re-send
the 
>transaction (since you didn't get a successful response) but it causes 
>duplication.

>It would all be fine if the response communication worked -- but 
>apparently it isn't...?


Kim Mitchell  - Web Designer/Programmer Analyst
United Heritage - PO Box 7777 - Meridian, ID 83680-7777 - Tel
208.475.0942 - 800.657.6351 - Fax 208.475.1042 -
kgibson@xxxxxxxxxxxxxxxxxx



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