Bug 378225 - [ipad][Android] JavaScript tests not working when using jetty/ClientResourcesServiceHandler
Summary: [ipad][Android] JavaScript tests not working when using jetty/ClientResources...
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 323033
  Show dependency tree
 
Reported: 2012-05-02 05:52 EDT by Tim Buschtoens CLA
Modified: 2012-05-14 09:11 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2012-05-02 05:52:34 EDT
The RAP javascript tests are not loading/starting correctly on the ipad if they are delivered by jetty/ClientResourcesServiceHandler. Apparently certain js-files are randomly delivered incompletely. As a result there are random javascript error message shown instead of the TestRunner. Sometimes its works a few times, then crashes again. The console prints errors like this:

2012-04-25 11:39:51.120:WARN:oejs.AsyncHttpConnection:Closing EndPoint making
no progress: 200
SCEP@395cb843{/192.168.17.103:49833->/192.168.17.111:8081,d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=false,i=5r}
AsyncHttpConnection@183000a5//192.168.17.111:8081<->192.168.17.103:49833,g=HttpGenerator{s=3,h=-1,b=32496,c=-1},p=HttpParser{s=0,l=10,c=0},r=3

It works fine when using apache instead of jetty, which is why i commited 3 files to be able to run the tests using apache:
- index-static.html
- appearance.js
- rap-org.eclipse.swt.theme.Fallback.js

All in the htdocs folder. They should be deleted when we fixed this issue.
Comment 1 Ivan Furnadjiev CLA 2012-05-02 05:59:25 EDT
Tim, is this a different issue - bug 374417?
Comment 2 Tim Buschtoens CLA 2012-05-02 10:07:22 EDT
Bug 374417 was fixed using an unsatisfying workaround. This bug is about removing the workaround when the core issue is solved. The other issues of Bug 374417 are fixed for real.
Comment 3 Tim Buschtoens CLA 2012-05-02 10:09:30 EDT
Got he exact same issue with my Android 2.3 cellphone! (Android 3 is ok.)