4 Replies Latest reply on Oct 28, 2010 7:57 AM by Zolotoj

    Help with run time error

    Zolotoj Level 3

      Error: Error #1502: A script has executed for longer than the default timeout period of 15 seconds.

      at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::getFocusObject()

      at mx.core::UIComponent/drawFocus()

      at mx.core::UIComponent/focusOutHandler()

      at mx.controls::Button/focusOutHandler()

      at flash.external::ExternalInterface$/_evalJS()

      at flash.external::ExternalInterface$/call()

      at BoxingPillows/resetLocalScannerServer()

      at BoxingPillows/__scanner_click()


      What can a reason be for it?



        • 1. Re: Help with run time error
          BhaskerChari Level 4

          Hi Zolotoj,


          Somewhere in your code is executing repeatedly and going into recursion, since Flash Player maximum timeout period is 15 seconds and exceeded the error is thrown.


          Try to debug your script and check where your code is failing.





          • 2. Re: Help with run time error
            Zolotoj Level 3

            I wish I knew where to put the debugging code.

            My application is running on 4 computers and only one has that problem. Three others had never have this problem.

            Is there any kind of technique I could use to track such activity you are mentioning?



            • 3. Re: Help with run time error
              Gaurav J Adobe Employee

              Is the machine where it shows up slower than the other machines?


              May be you should try performance profiling using the flex profiler and see where the hot spots are in your application.



              Gaurav Jain

              Flex SDK Team


              • 4. Re: Help with run time error
                Zolotoj Level 3

                A bit more details. What my application does is it listens to about 6 wireless devices with serial scanners attached to. These wireless devices have IPs and and ports. I am using the same port on all devices. I use  a Socket class. It is very possible that sometimes two or even more scans are hitting the app. in the time. I dont have any queue logic in place, I am assuming that Flex can handle it on its own. Am I wrong?