Announcement

Collapse
No announcement yet.

MvCALL Times Out

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    MvCALL Times Out



    ------=_NextPart_000_0012_01C4FE08.21D1AF40
    Content-Type: multipart/alternative;
    boundary="----=_NextPart_001_0013_01C4FE08.21D1AF40"


    ------=_NextPart_001_0013_01C4FE08.21D1AF40
    Content-Type: text/plain;
    charset="Windows-1252"
    Content-Transfer-Encoding: quoted-printable

    Out of a few thousand external URL's which I MvCALL, there are a very =
    few which cause the MvCALL statement to time out.

    I have asked my ISP to set the calltimeout value to be 60 in miva.conf =
    but still, when I MvCALL some sites, the entire script simply times out =
    - i.e. the script runs to its global timeout value and seems to ignore =
    the MvCALL timeout value.

    One site which I know will time out the script is at

    <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

    If I try to MvCALL it I always get 'script timeout' in spite of setting=20

    <MIVA MvCALL_ERROR=3D"nonfatal,nodisplay">

    and trying to test the MvCALL_ERROR value.

    Is there any way round this problem?

    Regards=20
    =20
    John Tuach=20
    UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for details)=20


    ------=_NextPart_001_0013_01C4FE08.21D1AF40
    Content-Type: text/html;
    charset="Windows-1252"
    Content-Transfer-Encoding: quoted-printable

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <HTML><HEAD>
    <META http-equiv=3DContent-Type content=3D"text/html; =
    charset=3Dwindows-1252"><BASE=20
    href=3D"file://C:Program FilesCommon FilesMicrosoft =
    SharedStationery">
    <STYLE>BODY {
    BACKGROUND-POSITION: left top; FONT-SIZE: 10pt; COLOR: blue; =
    BACKGROUND-REPEAT: no-repeat; FONT-FAMILY: Comic Sans MS
    }
    </STYLE>

    <META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR></HEAD>
    <BODY bgColor=3D#fffff0>
    <DIV>Out of a few thousand external URL's which I MvCALL, there are a =
    very few=20
    which cause the MvCALL statement to time out.</DIV>
    <DIV> </DIV>
    <DIV>I have asked my ISP to set the calltimeout value to be 60 in =
    miva.conf but=20
    still, when I MvCALL some sites, the entire script simply times =
    out - i.e.=20
    the script runs to its global timeout value and seems to ignore the =
    MvCALL=20
    timeout value.</DIV>
    <DIV> </DIV>
    <DIV>One site which I know will time out the script is at</DIV>
    <DIV> </DIV>
    <DIV><A=20
    href=3D"<A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A><=">http://www.simply-travel.com/">http://www.simply-travel.com/</A><=</A>
    /DIV>
    <DIV> </DIV>
    <DIV>If I try to MvCALL it I always get 'script timeout' in spite of =
    setting=20
    </DIV>
    <DIV> </DIV>
    <DIV><MIVA MvCALL_ERROR=3D"nonfatal,nodisplay">
    </DIV>
    <DIV>and trying to test the MvCALL_ERROR value.</DIV>
    <DIV> </DIV>
    <DIV>Is there any way round this problem?</DIV>
    <DIV> </DIV>
    <DIV>Regards </DIV>


    <IMG height=3D65 src=3D"<A HREF ="http://www.uk-golfguide.com/images/sig.gif" =">http://www.uk-golfguide.com/images/sig.gif" =</A>
    width=3D138>=20

    John Tuach
    UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. <A=20
    href=3D"<A HREF ="http://www.uk-golfguide.com/inthenews.html">Click for =">http://www.uk-golfguide.com/inthenews.html">Click for =</A>
    details</A>)=20

    </P></BODY></HTML>

    ------=_NextPart_001_0013_01C4FE08.21D1AF40--

    ------=_NextPart_000_0012_01C4FE08.21D1AF40--

    #2
    MvCALL Times Out



    ------=_NextPart_000_0008_01C4FE17.2B3BAA90
    Content-Type: text/plain;
    charset="us-ascii"
    Content-Transfer-Encoding: 7bit

    John,

    Unfortunately, the answer is no. MvCALL has a long-time bug which prevents
    proper error handling once you are within the MvCALL loop. What you could do
    is to check for the response headers of the MvCalled page, and add a manual
    MvCALLSTOP if it is something like 404 or Page not Found. This can (maybe)
    work in some cases.

    Another approach which at least can prevent these errors in the future is to
    flag those unavailable pages in your database. Since your script times out
    and wouldn't allow you to do any further action after the timeout, the trick
    is to first check in the database if the website is flagged, if it is not,
    flag it as unavailable, then call it, if it is reached, set the flag back to
    zero.

    Markus



    _____

    From: [email protected] [mailto:[email protected]] On Behalf
    Of John Tuach
    Sent: Wednesday, January 19, 2005 4:21 AM
    To: [email protected]
    Subject: [meu] MvCALL Times Out


    Out of a few thousand external URL's which I MvCALL, there are a very few
    which cause the MvCALL statement to time out.

    I have asked my ISP to set the calltimeout value to be 60 in miva.conf but
    still, when I MvCALL some sites, the entire script simply times out - i.e.
    the script runs to its global timeout value and seems to ignore the MvCALL
    timeout value.

    One site which I know will time out the script is at

    <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

    If I try to MvCALL it I always get 'script timeout' in spite of setting

    <MIVA MvCALL_ERROR="nonfatal,nodisplay">

    and trying to test the MvCALL_ERROR value.

    Is there any way round this problem?

    Regards

    <<A HREF ="http://www.uk-golfguide.com/images/sig.gif> ">http://www.uk-golfguide.com/images/sig.gif> </A>
    John Tuach
    UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for details
    <<A HREF ="http://www.uk-golfguide.com/inthenews.html> ) ">http://www.uk-golfguide.com/inthenews.html> ) </A>



    ------=_NextPart_000_0008_01C4FE17.2B3BAA90--

    Comment


      #3
      MvCALL Times Out



      ------=_NextPart_000_021E_01C4FE42.95AC2500
      Content-Type: text/plain;
      charset="iso-8859-1"
      Content-Transfer-Encoding: quoted-printable

      Thanks Markus

      If MvCALL decides to time out then no headers or any callvalues are =
      returned - in fact nothing is returned at all! I assume that Miva Corp =
      are not interested in fixing the bug?

      Just had a thought - given that I am MvDO'ing the MvCALL script maybe I =
      will try trapping the MvDO_error.


      ----- Original Message -----=20
      From: MvMarkus=20
      To: 'John Tuach' ; [email protected]=20
      Sent: Wednesday, January 19, 2005 4:07 PM
      Subject: RE: [meu] MvCALL Times Out


      John,

      Unfortunately, the answer is no. MvCALL has a long-time bug which =
      prevents proper error handling once you are within the MvCALL loop. What =
      you could do is to check for the response headers of the MvCalled page, =
      and add a manual MvCALLSTOP if it is something like 404 or Page not =
      Found. This can (maybe) work in some cases.=20

      Another approach which at least can prevent these errors in the future =
      is to flag those unavailable pages in your database. Since your script =
      times out and wouldn't allow you to do any further action after the =
      timeout, the trick is to first check in the database if the website is =
      flagged, if it is not, flag it as unavailable, then call it, if it is =
      reached, set the flag back to zero.=20

      Markus




      -------------------------------------------------------------------------=
      -----
      From: [email protected] [mailto:[email protected]] On =
      Behalf Of John Tuach
      Sent: Wednesday, January 19, 2005 4:21 AM
      To: [email protected]
      Subject: [meu] MvCALL Times Out


      Out of a few thousand external URL's which I MvCALL, there are a very =
      few which cause the MvCALL statement to time out.

      I have asked my ISP to set the calltimeout value to be 60 in miva.conf =
      but still, when I MvCALL some sites, the entire script simply times out =
      - i.e. the script runs to its global timeout value and seems to ignore =
      the MvCALL timeout value.

      One site which I know will time out the script is at

      <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

      If I try to MvCALL it I always get 'script timeout' in spite of =
      setting=20

      <MIVA MvCALL_ERROR=3D"nonfatal,nodisplay">

      and trying to test the MvCALL_ERROR value.

      Is there any way round this problem?

      Regards=20
      =20
      John Tuach=20
      UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for details)=20


      ------=_NextPart_000_021E_01C4FE42.95AC2500--

      Comment


        #4
        MvCALL Times Out



        ------=_NextPart_000_0071_01C4FE24.4DD8FB40
        Content-Type: text/plain;
        charset="us-ascii"
        Content-Transfer-Encoding: 7bit

        Hi John,

        The MvDO trick won't work, because it'll still wait until the MvCALL returns
        a result - as long until the script times out.

        The bug has been reported many times, and Jeffrey Collins demonstrated
        clearly that there is no workaround. Miva Corp does not acknowledge it and
        has -so
        far- shown no interest to fix it.

        Markus


        _____

        From: John Tuach [mailto:[email protected]]
        Sent: Wednesday, January 19, 2005 11:19 AM
        To: MvMarkus; [email protected]
        Subject: Re: [meu] MvCALL Times Out


        Thanks Markus

        If MvCALL decides to time out then no headers or any callvalues are returned
        - in fact nothing is returned at all! I assume that Miva Corp are not
        interested in fixing the bug?

        Just had a thought - given that I am MvDO'ing the MvCALL script maybe I will
        try trapping the MvDO_error.



        ----- Original Message -----
        From: MvMarkus <mailto:[email protected]>
        To: 'John Tuach' <mailto:[email protected]> ; [email protected]
        Sent: Wednesday, January 19, 2005 4:07 PM
        Subject: RE: [meu] MvCALL Times Out

        John,

        Unfortunately, the answer is no. MvCALL has a long-time bug which prevents
        proper error handling once you are within the MvCALL loop. What you could do
        is to check for the response headers of the MvCalled page, and add a manual
        MvCALLSTOP if it is something like 404 or Page not Found. This can (maybe)
        work in some cases.

        Another approach which at least can prevent these errors in the future is to
        flag those unavailable pages in your database. Since your script times out
        and wouldn't allow you to do any further action after the timeout, the trick
        is to first check in the database if the website is flagged, if it is not,
        flag it as unavailable, then call it, if it is reached, set the flag back to
        zero.

        Markus



        _____

        From: [email protected] [mailto:[email protected]] On Behalf
        Of John Tuach
        Sent: Wednesday, January 19, 2005 4:21 AM
        To: [email protected]
        Subject: [meu] MvCALL Times Out


        Out of a few thousand external URL's which I MvCALL, there are a very few
        which cause the MvCALL statement to time out.

        I have asked my ISP to set the calltimeout value to be 60 in miva.conf but
        still, when I MvCALL some sites, the entire script simply times out - i.e.
        the script runs to its global timeout value and seems to ignore the MvCALL
        timeout value.

        One site which I know will time out the script is at

        <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

        If I try to MvCALL it I always get 'script timeout' in spite of setting

        <MIVA MvCALL_ERROR="nonfatal,nodisplay">

        and trying to test the MvCALL_ERROR value.

        Is there any way round this problem?

        Regards

        <<A HREF ="http://www.uk-golfguide.com/images/sig.gif> ">http://www.uk-golfguide.com/images/sig.gif> </A>
        John Tuach
        UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for
        <<A HREF ="http://www.uk-golfguide.com/inthenews.html> details) ">http://www.uk-golfguide.com/inthenews.html> details) </A>



        ------=_NextPart_000_0071_01C4FE24.4DD8FB40--

        Comment


          #5
          MvCALL Times Out



          ------=_NextPart_000_0012_01C4FE5B.3E3D4BA0
          Content-Type: text/plain;
          charset="iso-8859-1"
          Content-Transfer-Encoding: quoted-printable

          Thanks for the info.

          I did try trapping the MvDO and yes, it never gets back to the parent =
          script.

          I now have a workaround where I write an empty 'URL specific' control =
          file before each MvCALL and if MvCALL terminates nicely, it deletes the =
          control file. A test before each MvCALL checks for the existence of the =
          control file and if true, MvCALL is skipped.

          Be easier if MvCALL_ERROR worked!

          Regards

          John Tuach

          ----- Original Message -----=20
          From: MvMarkus=20
          To: 'John Tuach' ; [email protected]=20
          Sent: Wednesday, January 19, 2005 5:42 PM
          Subject: RE: [meu] MvCALL Times Out


          Hi John,
          =20
          The MvDO trick won't work, because it'll still wait until the MvCALL =
          returns
          a result - as long until the script times out.=20
          =20
          The bug has been reported many times, and Jeffrey Collins demonstrated
          clearly that there is no workaround. Miva Corp does not acknowledge it =
          and
          has -so=20
          far- shown no interest to fix it.=20
          =20
          Markus
          =20

          _____ =20

          From: John Tuach [mailto:[email protected]]=20
          Sent: Wednesday, January 19, 2005 11:19 AM
          To: MvMarkus; [email protected]
          Subject: Re: [meu] MvCALL Times Out


          Thanks Markus
          =20
          If MvCALL decides to time out then no headers or any callvalues are =
          returned
          - in fact nothing is returned at all! I assume that Miva Corp are not
          interested in fixing the bug?
          =20
          Just had a thought - given that I am MvDO'ing the MvCALL script maybe =
          I will
          try trapping the MvDO_error.
          =20
          =20

          ----- Original Message -----=20
          From: MvMarkus <mailto:[email protected]> =20
          To: 'John Tuach' <mailto:[email protected]> ; =
          [email protected]=20
          Sent: Wednesday, January 19, 2005 4:07 PM
          Subject: RE: [meu] MvCALL Times Out

          John,
          =20
          Unfortunately, the answer is no. MvCALL has a long-time bug which =
          prevents
          proper error handling once you are within the MvCALL loop. What you =
          could do
          is to check for the response headers of the MvCalled page, and add a =
          manual
          MvCALLSTOP if it is something like 404 or Page not Found. This can =
          (maybe)
          work in some cases.=20
          =20
          Another approach which at least can prevent these errors in the future =
          is to
          flag those unavailable pages in your database. Since your script times =
          out
          and wouldn't allow you to do any further action after the timeout, the =
          trick
          is to first check in the database if the website is flagged, if it is =
          not,
          flag it as unavailable, then call it, if it is reached, set the flag =
          back to
          zero.=20
          =20
          Markus
          =20


          _____ =20

          From: [email protected] [mailto:[email protected]] On =
          Behalf
          Of John Tuach
          Sent: Wednesday, January 19, 2005 4:21 AM
          To: [email protected]
          Subject: [meu] MvCALL Times Out


          Out of a few thousand external URL's which I MvCALL, there are a very =
          few
          which cause the MvCALL statement to time out.
          =20
          I have asked my ISP to set the calltimeout value to be 60 in miva.conf =
          but
          still, when I MvCALL some sites, the entire script simply times out - =
          i.e.
          the script runs to its global timeout value and seems to ignore the =
          MvCALL
          timeout value.
          =20
          One site which I know will time out the script is at
          =20
          <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>
          =20
          If I try to MvCALL it I always get 'script timeout' in spite of =
          setting=20
          =20
          <MIVA MvCALL_ERROR=3D"nonfatal,nodisplay">

          and trying to test the MvCALL_ERROR value.
          =20
          Is there any way round this problem?
          =20
          Regards=20

          <<A HREF ="http://www.uk-golfguide.com/images/sig.gif>=20">http://www.uk-golfguide.com/images/sig.gif>=20</A>
          John Tuach=20
          UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for
          <<A HREF ="http://www.uk-golfguide.com/inthenews.html> details)=20">http://www.uk-golfguide.com/inthenews.html> details)=20</A>



          ------=_NextPart_000_0012_01C4FE5B.3E3D4BA0--

          Comment


            #6
            MvCALL Times Out



            "Be easier if MvCALL_ERROR worked!"

            That's definitely true - especially in regards of using MvCALL in
            conjunction with a payment gateway. This is really the reason why I don't
            understand that this doesn't get fixed. An unchecked timeout during checkout
            is "a big deal".

            Markus



            ________________________________

            From: John Tuach [mailto:[email protected]]
            Sent: Wednesday, January 19, 2005 2:16 PM
            To: MvMarkus; [email protected]
            Subject: Re: [meu] MvCALL Times Out


            Thanks for the info.

            I did try trapping the MvDO and yes, it never gets back to the parent
            script.

            I now have a workaround where I write an empty 'URL specific' control file
            before each MvCALL and if MvCALL terminates nicely, it deletes the control
            file. A test before each MvCALL checks for the existence of the control file
            and if true, MvCALL is skipped.

            Be easier if MvCALL_ERROR worked!

            Regards

            John Tuach


            ----- Original Message -----
            From: MvMarkus <mailto:[email protected]>
            To: 'John Tuach' <mailto:[email protected]> ;
            [email protected]
            Sent: Wednesday, January 19, 2005 5:42 PM
            Subject: RE: [meu] MvCALL Times Out

            Hi John,

            The MvDO trick won't work, because it'll still wait until the MvCALL
            returns
            a result - as long until the script times out.

            The bug has been reported many times, and Jeffrey Collins
            demonstrated
            clearly that there is no workaround. Miva Corp does not acknowledge
            it and
            has -so
            far- shown no interest to fix it.

            Markus


            _____

            From: John Tuach [mailto:[email protected]]
            Sent: Wednesday, January 19, 2005 11:19 AM
            To: MvMarkus; [email protected]
            Subject: Re: [meu] MvCALL Times Out


            Thanks Markus

            If MvCALL decides to time out then no headers or any callvalues are
            returned
            - in fact nothing is returned at all! I assume that Miva Corp are
            not
            interested in fixing the bug?

            Just had a thought - given that I am MvDO'ing the MvCALL script
            maybe I will
            try trapping the MvDO_error.



            ----- Original Message -----
            From: MvMarkus <mailto:[email protected]>
            To: 'John Tuach' <mailto:[email protected]> ;
            [email protected]
            Sent: Wednesday, January 19, 2005 4:07 PM
            Subject: RE: [meu] MvCALL Times Out

            John,

            Unfortunately, the answer is no. MvCALL has a long-time bug which
            prevents
            proper error handling once you are within the MvCALL loop. What you
            could do
            is to check for the response headers of the MvCalled page, and add a
            manual
            MvCALLSTOP if it is something like 404 or Page not Found. This can
            (maybe)
            work in some cases.

            Another approach which at least can prevent these errors in the
            future is to
            flag those unavailable pages in your database. Since your script
            times out
            and wouldn't allow you to do any further action after the timeout,
            the trick
            is to first check in the database if the website is flagged, if it
            is not,
            flag it as unavailable, then call it, if it is reached, set the flag
            back to
            zero.

            Markus



            _____

            From: [email protected] [mailto:[email protected]]
            On Behalf
            Of John Tuach
            Sent: Wednesday, January 19, 2005 4:21 AM
            To: [email protected]
            Subject: [meu] MvCALL Times Out


            Out of a few thousand external URL's which I MvCALL, there are a
            very few
            which cause the MvCALL statement to time out.

            I have asked my ISP to set the calltimeout value to be 60 in
            miva.conf but
            still, when I MvCALL some sites, the entire script simply times out
            - i.e.
            the script runs to its global timeout value and seems to ignore the
            MvCALL
            timeout value.

            One site which I know will time out the script is at

            <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

            If I try to MvCALL it I always get 'script timeout' in spite of
            setting

            <MIVA MvCALL_ERROR="nonfatal,nodisplay">

            and trying to test the MvCALL_ERROR value.

            Is there any way round this problem?

            Regards

            <<A HREF ="http://www.uk-golfguide.com/images/sig.gif> ">http://www.uk-golfguide.com/images/sig.gif> </A>
            John Tuach
            UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for
            <<A HREF ="http://www.uk-golfguide.com/inthenews.html> details) ">http://www.uk-golfguide.com/inthenews.html> details) </A>






            Comment


              #7
              MvCALL Times Out



              Not sure if it is this case, but problems with MvCALL are very often caused
              by wrong Empresa configuration - setting the calltimeout too _long_.
              Calltimeout should always be just a fraction of the globaltimeout. Best is
              keeping it within 10-15 seconds. The timer is being reset each time Empresa
              gets a packet from the remote URL, so there is no reason to have a longer
              timeout, unless you relay the connection through the Cassini spacecraft.
              Making calltimeout too long will definitely cause the globaltimeout to be
              triggered before and hence losing the chance to read the MvCALL error in the
              script.

              Well, there are still some pages that trigger a runtime error in MvCALL, and
              (although I never saw it) there may be also ones that cause timeout you
              mention. I would be curious to see an example of a URL that causes the
              timeout.

              Ivo
              http://mivo.truxoft.com


              -----Original Message-----
              From: MvMarkus


              "Be easier if MvCALL_ERROR worked!"

              That's definitely true - especially in regards of using MvCALL in
              conjunction with a payment gateway. This is really the reason why I don't
              understand that this doesn't get fixed. An unchecked timeout during checkout
              is "a big deal".

              Markus



              ________________________________

              From: John Tuach [mailto:[email protected]]
              Sent: Wednesday, January 19, 2005 2:16 PM
              To: MvMarkus; [email protected]
              Subject: Re: [meu] MvCALL Times Out


              Thanks for the info.

              I did try trapping the MvDO and yes, it never gets back to the parent
              script.

              I now have a workaround where I write an empty 'URL specific' control file
              before each MvCALL and if MvCALL terminates nicely, it deletes the control
              file. A test before each MvCALL checks for the existence of the control file
              and if true, MvCALL is skipped.

              Be easier if MvCALL_ERROR worked!

              Regards

              John Tuach


              ----- Original Message -----
              From: MvMarkus <mailto:[email protected]>
              To: 'John Tuach' <mailto:[email protected]> ;
              [email protected]
              Sent: Wednesday, January 19, 2005 5:42 PM
              Subject: RE: [meu] MvCALL Times Out

              Hi John,

              The MvDO trick won't work, because it'll still wait until the MvCALL
              returns
              a result - as long until the script times out.

              The bug has been reported many times, and Jeffrey Collins
              demonstrated
              clearly that there is no workaround. Miva Corp does not acknowledge
              it and
              has -so
              far- shown no interest to fix it.

              Markus


              _____

              From: John Tuach [mailto:[email protected]]
              Sent: Wednesday, January 19, 2005 11:19 AM
              To: MvMarkus; [email protected]
              Subject: Re: [meu] MvCALL Times Out


              Thanks Markus

              If MvCALL decides to time out then no headers or any callvalues are
              returned
              - in fact nothing is returned at all! I assume that Miva Corp are
              not
              interested in fixing the bug?

              Just had a thought - given that I am MvDO'ing the MvCALL script
              maybe I will
              try trapping the MvDO_error.



              ----- Original Message -----
              From: MvMarkus <mailto:[email protected]>
              To: 'John Tuach' <mailto:[email protected]> ;
              [email protected]
              Sent: Wednesday, January 19, 2005 4:07 PM
              Subject: RE: [meu] MvCALL Times Out

              John,

              Unfortunately, the answer is no. MvCALL has a long-time bug which
              prevents
              proper error handling once you are within the MvCALL loop. What you
              could do
              is to check for the response headers of the MvCalled page, and add a
              manual
              MvCALLSTOP if it is something like 404 or Page not Found. This can
              (maybe)
              work in some cases.

              Another approach which at least can prevent these errors in the
              future is to
              flag those unavailable pages in your database. Since your script
              times out
              and wouldn't allow you to do any further action after the timeout,
              the trick
              is to first check in the database if the website is flagged, if it
              is not,
              flag it as unavailable, then call it, if it is reached, set the flag
              back to
              zero.

              Markus



              _____

              From: [email protected] [mailto:[email protected]]
              On Behalf
              Of John Tuach
              Sent: Wednesday, January 19, 2005 4:21 AM
              To: [email protected]
              Subject: [meu] MvCALL Times Out


              Out of a few thousand external URL's which I MvCALL, there are a
              very few
              which cause the MvCALL statement to time out.

              I have asked my ISP to set the calltimeout value to be 60 in
              miva.conf but
              still, when I MvCALL some sites, the entire script simply times out
              - i.e.
              the script runs to its global timeout value and seems to ignore the
              MvCALL
              timeout value.

              One site which I know will time out the script is at

              <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

              If I try to MvCALL it I always get 'script timeout' in spite of
              setting

              <MIVA MvCALL_ERROR="nonfatal,nodisplay">

              and trying to test the MvCALL_ERROR value.

              Is there any way round this problem?

              Regards

              <<A HREF ="http://www.uk-golfguide.com/images/sig.gif> ">http://www.uk-golfguide.com/images/sig.gif> </A>
              John Tuach
              UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for
              <<A HREF ="http://www.uk-golfguide.com/inthenews.html> details) ">http://www.uk-golfguide.com/inthenews.html> details) </A>






              Comment


                #8
                MvCALL Times Out



                ------=_NextPart_000_0021_01C4FEC7.A1B72D60
                Content-Type: text/plain;
                charset="iso-8859-1"
                Content-Transfer-Encoding: quoted-printable

                Morning Ivo...

                Having checked with Cybrmall a few days ago, the globaltimeout value in =
                miva.conf is=20

                globaltimeout=3D150

                and I asked that they set the calltimeout to be 60 which they now have =
                done.

                The site at=20

                <A HREF ="http://www.simply-travel.com/simply/simply.asp">http://www.simply-travel.com/simply/simply.asp</A>

                always results in a script timeout on the live server although not if I =
                run the same script on my local server using MivaMia.

                ----- Original Message -----=20
                From: Ivo Truxa=20
                To: [email protected]=20
                Sent: Wednesday, January 19, 2005 11:29 PM
                Subject: RE: [meu] MvCALL Times Out


                Not sure if it is this case, but problems with MvCALL are very often =
                caused
                by wrong Empresa configuration - setting the calltimeout too _long_.
                Calltimeout should always be just a fraction of the globaltimeout. =
                Best is
                keeping it within 10-15 seconds. The timer is being reset each time =
                Empresa
                gets a packet from the remote URL, so there is no reason to have a =
                longer
                timeout, unless you relay the connection through the Cassini =
                spacecraft.
                Making calltimeout too long will definitely cause the globaltimeout to =
                be
                triggered before and hence losing the chance to read the MvCALL error =
                in the
                script.

                Well, there are still some pages that trigger a runtime error in =
                MvCALL, and
                (although I never saw it) there may be also ones that cause timeout =
                you
                mention. I would be curious to see an example of a URL that causes the
                timeout.

                Ivo
                http://mivo.truxoft.com=20


                -----Original Message-----
                From: MvMarkus


                "Be easier if MvCALL_ERROR worked!"
                =20
                That's definitely true - especially in regards of using MvCALL in
                conjunction with a payment gateway. This is really the reason why I =
                don't
                understand that this doesn't get fixed. An unchecked timeout during =
                checkout
                is "a big deal".
                =20
                Markus
                =20
                =20

                ________________________________

                From: John Tuach [mailto:[email protected]]=20
                Sent: Wednesday, January 19, 2005 2:16 PM
                To: MvMarkus; [email protected]
                Subject: Re: [meu] MvCALL Times Out


                Thanks for the info.
                =20
                I did try trapping the MvDO and yes, it never gets back to the parent
                script.
                =20
                I now have a workaround where I write an empty 'URL specific' control =
                file
                before each MvCALL and if MvCALL terminates nicely, it deletes the =
                control
                file. A test before each MvCALL checks for the existence of the =
                control file
                and if true, MvCALL is skipped.
                =20
                Be easier if MvCALL_ERROR worked!
                =20
                Regards
                =20
                John Tuach
                =20

                ----- Original Message -----=20
                From: MvMarkus <mailto:[email protected]> =20
                To: 'John Tuach' <mailto:[email protected]> ;
                [email protected]=20
                Sent: Wednesday, January 19, 2005 5:42 PM
                Subject: RE: [meu] MvCALL Times Out

                Hi John,

                The MvDO trick won't work, because it'll still wait until the MvCALL
                returns
                a result - as long until the script times out.=20

                The bug has been reported many times, and Jeffrey Collins
                demonstrated
                clearly that there is no workaround. Miva Corp does not acknowledge
                it and
                has -so=20
                far- shown no interest to fix it.=20

                Markus


                _____ =20

                From: John Tuach [mailto:[email protected]]=20
                Sent: Wednesday, January 19, 2005 11:19 AM
                To: MvMarkus; [email protected]
                Subject: Re: [meu] MvCALL Times Out


                Thanks Markus

                If MvCALL decides to time out then no headers or any callvalues are
                returned
                - in fact nothing is returned at all! I assume that Miva Corp are
                not
                interested in fixing the bug?

                Just had a thought - given that I am MvDO'ing the MvCALL script
                maybe I will
                try trapping the MvDO_error.



                ----- Original Message -----=20
                From: MvMarkus <mailto:[email protected]> =20
                To: 'John Tuach' <mailto:[email protected]> ;
                [email protected]=20
                Sent: Wednesday, January 19, 2005 4:07 PM
                Subject: RE: [meu] MvCALL Times Out

                John,

                Unfortunately, the answer is no. MvCALL has a long-time bug which
                prevents
                proper error handling once you are within the MvCALL loop. What you
                could do
                is to check for the response headers of the MvCalled page, and add a
                manual
                MvCALLSTOP if it is something like 404 or Page not Found. This can
                (maybe)
                work in some cases.=20

                Another approach which at least can prevent these errors in the
                future is to
                flag those unavailable pages in your database. Since your script
                times out
                and wouldn't allow you to do any further action after the timeout,
                the trick
                is to first check in the database if the website is flagged, if it
                is not,
                flag it as unavailable, then call it, if it is reached, set the flag
                back to
                zero.=20

                Markus



                _____ =20

                From: [email protected] [mailto:[email protected]]
                On Behalf
                Of John Tuach
                Sent: Wednesday, January 19, 2005 4:21 AM
                To: [email protected]
                Subject: [meu] MvCALL Times Out


                Out of a few thousand external URL's which I MvCALL, there are a
                very few
                which cause the MvCALL statement to time out.

                I have asked my ISP to set the calltimeout value to be 60 in
                miva.conf but
                still, when I MvCALL some sites, the entire script simply times out
                - i.e.
                the script runs to its global timeout value and seems to ignore the
                MvCALL
                timeout value.

                One site which I know will time out the script is at

                <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

                If I try to MvCALL it I always get 'script timeout' in spite of
                setting=20

                <MIVA MvCALL_ERROR=3D"nonfatal,nodisplay">

                and trying to test the MvCALL_ERROR value.

                Is there any way round this problem?

                Regards=20

                <<A HREF ="http://www.uk-golfguide.com/images/sig.gif>=20">http://www.uk-golfguide.com/images/sig.gif>=20</A>
                John Tuach=20
                UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for
                <<A HREF ="http://www.uk-golfguide.com/inthenews.html> details)=20">http://www.uk-golfguide.com/inthenews.html> details)=20</A>






                Comment


                  #9
                  MvCALL Times Out



                  The site seems to be located in the UK. I cannot access the URL even in a
                  browser here from the Old Continent, so it is not a wonder you are having
                  problems from your server in the USA. I am not sure if the site blocks
                  foreign requests deliberately, or if it is just extremely sluggish.

                  However, as I already wrote, having the calltimeout longer than 10-15 secs
                  makes no sense, so your 60 secs are still far too high. You do not want that
                  your script waits for each unresponsive server 1 minute, especially if you
                  make several MvCALLs in the same script pass - that will lead to timing out
                  through the globaltimeout without any error from MvCALL again. If a server
                  does not start sending any data within a second or two, than it is usually
                  pretty safe to tell that the connection (or the server) does not work -
                  hence the calltimeout of 10-15 secs is more than sufficient reserve.

                  Ivo
                  http://mivo.truxoft.com


                  -----Original Message-----
                  From: John Tuach [mailto:[email protected]]

                  Morning Ivo...

                  Having checked with Cybrmall a few days ago, the globaltimeout value in
                  miva.conf is

                  globaltimeout=150

                  and I asked that they set the calltimeout to be 60 which they now have done.

                  The site at

                  <A HREF ="http://www.simply-travel.com/simply/simply.asp">http://www.simply-travel.com/simply/simply.asp</A>

                  always results in a script timeout on the live server although not if I run
                  the same script on my local server using MivaMia.

                  ----- Original Message -----

                  From: Ivo Truxa <mailto:[email protected]>
                  To: [email protected]
                  Sent: Wednesday, January 19, 2005 11:29 PM
                  Subject: RE: [meu] MvCALL Times Out


                  Not sure if it is this case, but problems with MvCALL are very often
                  caused
                  by wrong Empresa configuration - setting the calltimeout too _long_.
                  Calltimeout should always be just a fraction of the globaltimeout.
                  Best is
                  keeping it within 10-15 seconds. The timer is being reset each time
                  Empresa
                  gets a packet from the remote URL, so there is no reason to have a
                  longer
                  timeout, unless you relay the connection through the Cassini
                  spacecraft.
                  Making calltimeout too long will definitely cause the globaltimeout
                  to be
                  triggered before and hence losing the chance to read the MvCALL
                  error in the
                  script.

                  Well, there are still some pages that trigger a runtime error in
                  MvCALL, and
                  (although I never saw it) there may be also ones that cause timeout
                  you
                  mention. I would be curious to see an example of a URL that causes
                  the
                  timeout.

                  Ivo
                  http://mivo.truxoft.com


                  -----Original Message-----
                  From: MvMarkus


                  "Be easier if MvCALL_ERROR worked!"

                  That's definitely true - especially in regards of using MvCALL in
                  conjunction with a payment gateway. This is really the reason why I
                  don't
                  understand that this doesn't get fixed. An unchecked timeout during
                  checkout
                  is "a big deal".

                  Markus



                  ________________________________

                  From: John Tuach [mailto:[email protected]]
                  Sent: Wednesday, January 19, 2005 2:16 PM
                  To: MvMarkus; [email protected]
                  Subject: Re: [meu] MvCALL Times Out


                  Thanks for the info.

                  I did try trapping the MvDO and yes, it never gets back to the
                  parent
                  script.

                  I now have a workaround where I write an empty 'URL specific'
                  control file
                  before each MvCALL and if MvCALL terminates nicely, it deletes the
                  control
                  file. A test before each MvCALL checks for the existence of the
                  control file
                  and if true, MvCALL is skipped.

                  Be easier if MvCALL_ERROR worked!

                  Regards

                  John Tuach


                  ----- Original Message -----
                  From: MvMarkus <mailto:[email protected]>
                  To: 'John Tuach' <mailto:[email protected]> ;
                  [email protected]
                  Sent: Wednesday, January 19, 2005 5:42 PM
                  Subject: RE: [meu] MvCALL Times Out

                  Hi John,

                  The MvDO trick won't work, because it'll still wait until the MvCALL
                  returns
                  a result - as long until the script times out.

                  The bug has been reported many times, and Jeffrey Collins
                  demonstrated
                  clearly that there is no workaround. Miva Corp does not acknowledge
                  it and
                  has -so
                  far- shown no interest to fix it.

                  Markus


                  _____

                  From: John Tuach [mailto:[email protected]]
                  Sent: Wednesday, January 19, 2005 11:19 AM
                  To: MvMarkus; [email protected]
                  Subject: Re: [meu] MvCALL Times Out


                  Thanks Markus

                  If MvCALL decides to time out then no headers or any callvalues are
                  returned
                  - in fact nothing is returned at all! I assume that Miva Corp are
                  not
                  interested in fixing the bug?

                  Just had a thought - given that I am MvDO'ing the MvCALL script
                  maybe I will
                  try trapping the MvDO_error.



                  ----- Original Message -----
                  From: MvMarkus <mailto:[email protected]>
                  To: 'John Tuach' <mailto:[email protected]> ;
                  [email protected]
                  Sent: Wednesday, January 19, 2005 4:07 PM
                  Subject: RE: [meu] MvCALL Times Out

                  John,

                  Unfortunately, the answer is no. MvCALL has a long-time bug which
                  prevents
                  proper error handling once you are within the MvCALL loop. What you
                  could do
                  is to check for the response headers of the MvCalled page, and add a
                  manual
                  MvCALLSTOP if it is something like 404 or Page not Found. This can
                  (maybe)
                  work in some cases.

                  Another approach which at least can prevent these errors in the
                  future is to
                  flag those unavailable pages in your database. Since your script
                  times out
                  and wouldn't allow you to do any further action after the timeout,
                  the trick
                  is to first check in the database if the website is flagged, if it
                  is not,
                  flag it as unavailable, then call it, if it is reached, set the flag
                  back to
                  zero.

                  Markus



                  _____

                  From: [email protected] [mailto:[email protected]]
                  On Behalf
                  Of John Tuach
                  Sent: Wednesday, January 19, 2005 4:21 AM
                  To: [email protected]
                  Subject: [meu] MvCALL Times Out


                  Out of a few thousand external URL's which I MvCALL, there are a
                  very few
                  which cause the MvCALL statement to time out.

                  I have asked my ISP to set the calltimeout value to be 60 in
                  miva.conf but
                  still, when I MvCALL some sites, the entire script simply times out
                  - i.e.
                  the script runs to its global timeout value and seems to ignore the
                  MvCALL
                  timeout value.

                  One site which I know will time out the script is at

                  <A HREF ="http://www.simply-travel.com/">http://www.simply-travel.com/</A>

                  If I try to MvCALL it I always get 'script timeout' in spite of
                  setting

                  <MIVA MvCALL_ERROR="nonfatal,nodisplay">

                  and trying to test the MvCALL_ERROR value.

                  Is there any way round this problem?

                  Regards

                  <<A HREF ="http://www.uk-golfguide.com/images/sig.gif> ">http://www.uk-golfguide.com/images/sig.gif> </A>
                  John Tuach
                  UK-GolfGuide.com (PGA Magazine's 'Best of Breed'. Click for
                  <<A HREF ="http://www.uk-golfguide.com/inthenews.html> details) ">http://www.uk-golfguide.com/inthenews.html> details) </A>






                  Comment

                  Working...
                  X