I don't get any more luck with the source version of the app. I don't have a more detailed message
Le 11 avril 2012 08:48, Benjamin Dreux <[email protected]> a écrit : > Hi > I'm using qooxdoo 1.6, the stable last version > I'm getting the error from the browser, which says some request cannot > be retreived. > The assets which cannot be retreived is random. > The image retrived base on widget like atom or buttons(the icon property). > > I didn't try the source version. > I'll give it a try right the way > > Regards > Le 11 avril 2012 08:33, thron7 <[email protected]> a écrit : >> Your information is too vague. >> Which qooxdoo version are you using? >> Which exact error do you get, and from whom (qooxdoo, browser, backend, >> ....)? >> Which assets cause the timeout? Is it always the same (set of) assets, >> or are they randomly different? >> Which part of the application loads the assets? Are these images managed >> by the qooxdoo run time, or are you explicitly loading them from your >> application code? >> >> As the images are available with the next reload, I presume they arrive >> too late after the initial request, so it could be an issue with the >> timeout handling in the qooxdoo run time. Can you reproduce the issue >> with a source version of your app? If so, which console messages do you >> get, and from whom? >> >> T. >> >> On 04/11/2012 02:06 PM, Benjamin Dreux wrote: >>> Hi >>> After a while the error reappears. >>> >>> As far as i can tell, the error appears when the cache is empty. >>> Once the application is loaded a first time, with a loading error, the >>> next load time execute without error >>> >>> Do you have idea, when i can find my error. >>> I'm using chrome 18. >>> >>> When using firefox or safari, i have no issue with the images. >>> >>> Regards >>> >>> >>> Le 29 mars 2012 10:07, Benjamin Dreux<[email protected]> a écrit : >>>> Thanks for your kind advices. >>>> Finnaly it was noting really bug, just a class that was modifed on my >>>> working copy, and not on our ci servers. >>>> >>>> Regards >>>> >>>> Le 29 mars 2012 05:14, Pierre Dehaen<[email protected]> a écrit : >>>>> On 28 Mar 2012 at 10:40, Benjamin Dreux wrote: >>>>> >>>>>> Hi, we are building an app based on qooxdoo.Since a few days we have a >>>>>> problem with our application.When loading the app, some asset can't be >>>>>> retreived, from the server.The chrome dev util say's we got timeout or >>>>>> even 404. >>>>>> But on the logs on our server, everything looks normal. >>>>>> We think it could be some part of the our qooxdoo app that isresponsible >>>>>> for this behavior, but we can't find out where for now. >>>>>> Somethimes it's even worth's the internet connection is >>>>>> completlyunsabled, when loading the app. >>>>>> Do you have some piece of advice for us, on how to track down this issue. >>>>>> Thanks >>>>>> -- Benjamin DreuxAnalyste-ProgrammeurChaire de logiciel libre-Finance >>>>>> Social et solidaireUQAMMontréal >>>>>> ------------------------------------------------------------------------------This >>>>>> SF email is sponsosred by:Try Windows Azure free for 90 days Click Here >>>>>> http://p.sf.net/sfu/sfd2d-msazure_______________________________________________qooxdoo-devel >>>>>> mailing >>>>>> [email protected]https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>>>>> >>>>> Hi Benjamin, >>>>> >>>>> You can always truss (on Solaris) or strace (on linux) the web server >>>>> process to see what's >>>>> happening. You can also snoop (Solaris) or tcpdump (linux) or wireshark >>>>> (all) the >>>>> communication. Or, simpler, on the client with Firefox, you could install >>>>> the Live HTTP >>>>> Header plugin to see the communication going on the wire... >>>>> >>>>> Regards, >>>>> Pierre >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF email is sponsosred by: >>>>> Try Windows Azure free for 90 days Click Here >>>>> http://p.sf.net/sfu/sfd2d-msazure >>>>> _______________________________________________ >>>>> qooxdoo-devel mailing list >>>>> [email protected] >>>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>>> >>>> >>>> -- >>>> Benjamin Dreux >>>> Analyste-Programmeur >>>> Chaire de logiciel libre-Finance Social et solidaire >>>> UQAM >>>> Montréal >>> >>> >> >> ------------------------------------------------------------------------------ >> Better than sec? Nothing is better than sec when it comes to >> monitoring Big Data applications. Try Boundary one-second >> resolution app monitoring today. Free. >> http://p.sf.net/sfu/Boundary-dev2dev >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > > -- > Benjamin Dreux > Analyste-Programmeur > Chaire de logiciel libre-Finance Social et solidaire > UQAM > Montréal -- Benjamin Dreux Analyste-Programmeur Chaire de logiciel libre-Finance Social et solidaire UQAM Montréal ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
