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

Re: HTTP API issues with timing out

Kathleen,
If this works out for you, can you please post details of what you changed? This is a solution that I've not heard of before.
What do you mean by "larger reading buffer"? By default, HTTPAPI uses a 128k receive buffer when reading from the network (you are suggesting a 1k buffer as being larger, so you must mean something different?) 

-SK

On 11/10/2014 1:27 PM, OLeary, Kathleen wrote:

    Mike, thank you so much for reaching out - below is what we came up
    with, just for future referencing! We are a lottery and this was an
    issue we were having with processing scratch ticket inventory with a
    new vendor.
    Identified the problem with READR through a data file log we created
    for the buffers being read.�  It is related to volume, when more than
    one transaction gets stacked in the TCP buffer before GTECHREADR can
    receive them.
    The fix is to create a larger reading buffer (we are going to try 1024)
    and to parse that buffer into transactions.�

    Kathleen O'Leary� | IT Programming and Development�  Manager

    COLORADO LOTTERY
    225 N. Main Street, Pueblo CO 81003
    P 719 546-5300 |� F 719 546-5274 Cell 719-338-9206
    [1]www.coloradolottery.com

    On Mon, Nov 10, 2014 at 11:20 AM, Mike Krebs
    <[2]mkrebs@xxxxxxxxxxxxxxxxxx> wrote:

      Should it even take 15 seconds to complete?
      15 seconds is not the default in the newer versions. Are you setting
      the time-out to 15 seconds? Have you tried 60 seconds or some other
      number?
      Have you tried to ping the server in the new application?
      Does the debug show at what point the timeout is occurring?
      -----Original Message-----
      From: [3]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
      [mailto:[4]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
      OLeary, Kathleen
      Sent: Sunday, November 9, 2014 7:05 PM
      To: [5]ftpapi@xxxxxxxxxxxxxxxxxxxxxx; Kathleen OLeary
      Subject: HTTP API issues with timing out
      Scott, we are having issues today with a new application using HTTP
      API version 1.23. We are having time out issues every 15 seconds we
      are losing connection - it is being dropped between our system and
      our vendor. We are using TCP, not SSL.
      Would you have ANY suggestions on where to look??? Any help would be
      appreciated. Thanks!
      Kathleen O'Leary
      Kathleen O'Leary | IT Programming and Development�  Manager
      *COLORADO LOTTERY *
      225 N. Main Street, Pueblo CO 81003
      *P* [6]719 546-5300 | *F* [7]719 546-5274 Cell [8]719-338-9206
      *[9]www.coloradolottery.com <[10]http://www.coloradolottery.com>*
      --------------------------------------------------------------------
      ---
      This is the FTPAPI mailing list.�  To unsubscribe, please go to:
      [11]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
-----------------------------------------------------------------------