Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Crash with click in tree on one specific IE10(Crash with click in tree on one specific IE10)
Crash with click in tree on one specific IE10 [message #1062392] Fri, 07 June 2013 10:04 Go to next message
John Gymer is currently offline John Gymer
Messages: 185
Registered: November 2012
Location: UK
Senior Member
I have a RAP application working (what I thought was) reliably, but one particular customer connects to our demo application (they are in Holland) using a Win7 64-bit machine with Internet Explorer 10 (latest patches) and gets the following error reported on the OSGi server (we see this our end). They get the same problem from behind their company's firewall and directly from home too:

2013-06-07 13:08:02.421:WARN:oejs.ServletHandler:ERROR:  /demo;jsessionid=rlidtjjdb3264z4eg54gkzbx
java.lang.IllegalArgumentException: Not a valid integer number: 139.33334350585938
        at org.eclipse.rap.rwt.internal.util.NumberFormatUtil.parseInt(NumberFormatUtil.java:20)
        at org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.readEventIntProperty(ControlLCAUtil.java:617)
        at org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.readEventXYProperties(ControlLCAUtil.java:610)
        at org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.sendMouseEvent(ControlLCAUtil.java:142)
        at org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.processMouseEvents(ControlLCAUtil.java:125)
        at org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.processEvents(ControlLCAUtil.java:120)
        at org.eclipse.swt.internal.widgets.treekit.TreeLCA.readData(TreeLCA.java:142)
        at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA$1.doVisit(DisplayLCA.java:76)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor$AllWidgetTreeVisitor.visit(WidgetTreeVisitor.java:40)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:52)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.handleChildren(WidgetTreeVisitor.java:127)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:57)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.handleChildren(WidgetTreeVisitor.java:127)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:57)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.handleChildren(WidgetTreeVisitor.java:127)
        at org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:57)
        at org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readData(DisplayLCA.java:83)
        at org.eclipse.rap.rwt.internal.lifecycle.ReadData.execute(ReadData.java:26)
        at org.eclipse.rap.rwt.internal.lifecycle.PhaseExecutor.execute(PhaseExecutor.java:35)
        at org.eclipse.rap.rwt.internal.lifecycle.SimpleLifeCycle.execute(SimpleLifeCycle.java:51)
        at org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.runLifeCycle(LifeCycleServiceHandler.java:136)
        at org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.handlePostRequest(LifeCycleServiceHandler.java:122)
        at org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.synchronizedService(LifeCycleServiceHandler.java:75)
        at org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.service(LifeCycleServiceHandler.java:66)
        at org.eclipse.rap.rwt.engine.RWTServlet.handleValidRequest(RWTServlet.java:119)
        at org.eclipse.rap.rwt.engine.RWTServlet.handleRequest(RWTServlet.java:106)
        at org.eclipse.rap.rwt.engine.RWTServlet.doPost(RWTServlet.java:99)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
        at org.eclipse.rap.rwt.osgi.internal.CutOffContextPathWrapper.service(CutOffContextPathWrapper.java:106)
        at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
        at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:457)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
        at org.eclipse.jetty.server.Server.handle(Server.java:368)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
        at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:953)
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)

        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
        at java.lang.Thread.run(Thread.java:662)


We cannot reproduce this crash on any of our machines, with any browser, including some Win7 64-bit IET10 machines, which we believe are setup in almost the same manner.

I wonder whether anyone in the RAP team could comment on what this could be?

The problem occurs when the user clicks somewhere within a Tree control (anywhere in the control), and appears to be in the RAP/RWT runtime rather than in our code.

It is consistent for him, but we have never seen the problem ourselves.

Any help or pointers would be gratefully received!

We will try to put together a simpler test case to see if he still has the same problem, but in the meantime, if something in the above error looks useful, then please let me know!

You can follow this link to our demo app to try for yourself (assuming we have the OSGi server up!)... click on the "List Boxes" button and click somewhere in the listbox that appears:
http://80.177.61.42:81/demo

Thanks, John


---
Just because you can doesn't mean you should
Re: Crash with click in tree on one specific IE10 [message #1062399 is a reply to message #1062392] Fri, 07 June 2013 10:23 Go to previous messageGo to next message
Ivan Furnadjiev is currently offline Ivan Furnadjiev
Messages: 1773
Registered: July 2009
Senior Member
Hi John,
this issue has ben fixed in RAP 2.1 RC2. See:
408701: IllegalArgumentException: "Not a valid integer number" when
browser zoom < 100%(IE10)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=408701
Best,
Ivan

On 6/7/2013 5:04 PM, John Gymer wrote:
> I have a RAP application working (what I thought was) reliably, but
> one particular customer connects to our demo application (they are in
> Holland) using a Win7 64-bit machine with Internet Explorer 10 (latest
> patches) and gets the following error reported on the OSGi server (we
> see this our end). They get the same problem from behind their
> company's firewall and directly from home too:
>
>
> 2013-06-07 13:08:02.421:WARN:oejs.ServletHandler:ERROR:
> /demo;jsessionid=rlidtjjdb3264z4eg54gkzbx
> java.lang.IllegalArgumentException: Not a valid integer number:
> 139.33334350585938
> at
> org.eclipse.rap.rwt.internal.util.NumberFormatUtil.parseInt(NumberFormatUtil.java:20)
> at
> org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.readEventIntProperty(ControlLCAUtil.java:617)
> at
> org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.readEventXYProperties(ControlLCAUtil.java:610)
> at
> org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.sendMouseEvent(ControlLCAUtil.java:142)
> at
> org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.processMouseEvents(ControlLCAUtil.java:125)
> at
> org.eclipse.rap.rwt.lifecycle.ControlLCAUtil.processEvents(ControlLCAUtil.java:120)
> at
> org.eclipse.swt.internal.widgets.treekit.TreeLCA.readData(TreeLCA.java:142)
> at
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA$1.doVisit(DisplayLCA.java:76)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor$AllWidgetTreeVisitor.visit(WidgetTreeVisitor.java:40)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:52)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.handleChildren(WidgetTreeVisitor.java:127)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:57)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.handleChildren(WidgetTreeVisitor.java:127)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:57)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.handleChildren(WidgetTreeVisitor.java:127)
> at
> org.eclipse.swt.internal.widgets.WidgetTreeVisitor.accept(WidgetTreeVisitor.java:57)
> at
> org.eclipse.swt.internal.widgets.displaykit.DisplayLCA.readData(DisplayLCA.java:83)
> at
> org.eclipse.rap.rwt.internal.lifecycle.ReadData.execute(ReadData.java:26)
> at
> org.eclipse.rap.rwt.internal.lifecycle.PhaseExecutor.execute(PhaseExecutor.java:35)
> at
> org.eclipse.rap.rwt.internal.lifecycle.SimpleLifeCycle.execute(SimpleLifeCycle.java:51)
> at
> org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.runLifeCycle(LifeCycleServiceHandler.java:136)
> at
> org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.handlePostRequest(LifeCycleServiceHandler.java:122)
> at
> org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.synchronizedService(LifeCycleServiceHandler.java:75)
> at
> org.eclipse.rap.rwt.internal.service.LifeCycleServiceHandler.service(LifeCycleServiceHandler.java:66)
> at
> org.eclipse.rap.rwt.engine.RWTServlet.handleValidRequest(RWTServlet.java:119)
> at
> org.eclipse.rap.rwt.engine.RWTServlet.handleRequest(RWTServlet.java:106)
> at
> org.eclipse.rap.rwt.engine.RWTServlet.doPost(RWTServlet.java:99)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.rap.rwt.osgi.internal.CutOffContextPathWrapper.service(CutOffContextPathWrapper.java:106)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386)
> at
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:669)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:457)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384)
> at
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:368)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
> at
> org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:953)
> at
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014)
> at
> org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861)
> at
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
>
> at
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628)
> at
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:662)
>
>
> We cannot reproduce this crash on any of our machines, with any
> browser, including some Win7 64-bit IET10 machines, which we believe
> are setup in almost the same manner.
>
> I wonder whether anyone in the RAP team could comment on what this
> could be?
>
> The problem occurs when the user clicks somewhere within a Tree
> control (anywhere in the control), and appears to be in the RAP/RWT
> runtime rather than in our code.
>
> It is consistent for him, but we have never seen the problem ourselves.
>
> Any help or pointers would be gratefully received!
>
> We will try to put together a simpler test case to see if he still has
> the same problem, but in the meantime, if something in the above error
> looks useful, then please let me know!
>
> You can follow this link to our demo app to try for yourself (assuming
> we have the OSGi server up!)... click on the "List Boxes" button and
> click somewhere in the listbox that appears:
> http://80.177.61.42:81/demo
>
> Thanks, John
>

--
Ivan Furnadjiev

Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: Crash with click in tree on one specific IE10 [message #1062404 is a reply to message #1062399] Fri, 07 June 2013 10:32 Go to previous message
John Gymer is currently offline John Gymer
Messages: 185
Registered: November 2012
Location: UK
Senior Member
Thanks Ivan,
I'll need to wait until Tabris adopts RC2, but it does look like the same thing.
Cheers, John


---
Just because you can doesn't mean you should
Previous Topic:RAP and Tabris
Next Topic:[ANN] RAP 2.1 RC3 is available
Goto Forum:
  


Current Time: Wed Jul 23 10:13:10 EDT 2014

Powered by FUDForum. Page generated in 0.02776 seconds