network error 'previous request not completed'

[Mark Schonewille]

Hi Graham,

I posted this to the forum a few days ago:

     local lBusy
     on mouseUp
        put empty
        if lBusy is true then
           beep
           answer "Are you sure" with "Yes" or "No"
           if it is "No" then
              exit mouseUp
           else
              repeat for each line mySock in the openSockets
                 close socket mySock
              end repeat
              beep
           end if
        end if
        put true into lBusy
        put  "http://bla.bla.com" into myUrl
        post "hello" to url myUrl
        put the result into rslt
        put false into lBusy
        put "ok" & rslt
     end mouseUp

This script checks whether you're currently waiting for a response and 
resets the connection if you decide to continue. ResetAll didn't work, 
that's why I close the sockets. It should prevent the problem from 
occurring in at least a few cases. You might also adjust the script to 
only close the socket this script was trying to connect to.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab and other 
colour spaces. http://www.color-converter.com

Buy my new book "Programming LiveCode for the Real Beginner" 
http://qery.us/3fi

Fill out this survey please
http://livecodebeginner.economy-x-talk.com/survey/

On 6/19/2013 18:03, Graham Pearson wrote:
> Were you able to find a solution for this. I have just ran into this
> just today from an application that was working well.
>
>
>
> On 1/17/2012 7:04 PM, Terry Judd wrote:
>> I'm experiencing a serious connectivity problem that appears to start with the error 'error Previous request not completed', usually in response to a post request, and ends with LC being pretty much totally unresponsive to any network requests. In the IDE this can sometimes (but not always) be rectified by calling resetAll but in our application, the only solution is to quit the app and start again. The post request are via https but I'm not sure whether that's a factor. One of my beta testers is having real problems with this (on multiple platforms) but I'm unable to replicate the problem on my setup at the moment.
>>
>> The socketTimeoutInterval is set to 5000 but when the error occurs it will repeatedly occur no matter how long you wait between requests (once the error occurs network connectivity is pretty much broken).
>>
>> Anyone have any ideas as to what may be occurring? I really need to squash this problem/bug ASAP.
>>
>> Terry...
>>
>> Dr Terry Judd
>> Senior Lecturer in Medical Education
>> Medical Eduction Unit
>> Faculty of Medicine, Dentistry & Health Sciences
>> The University of Melbourne
>>