Path-to-root embedded view: Remote connection lost

[drusk]

I have been testing the path to root embedded view in Chrome and I get problems where Chrome reports "The following plug-in has crashed: GWT DMP Plugin". Then when I look in the Development mode tab in Eclipse I can see that there has been a "Remote Connection Lost" message: com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote connection lost at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:307) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:546) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:363) at java.lang.Thread.run(Thread.java:722) Caused by: java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) ....etc.

The entries previous to the Remote connection lost usually show response times which are getting progressively worse. For example, they start around 100ms then 500ms then 1000ms then sometimes up as high as 5000ms before crashing.

However, this happens at varying points in the execution. Often the root to path finishes loading, then this happens right away, probably as it automatically loads the concepts and mappings for expansion. If it survives through that, then clicking to expand concepts on a node usually finishes it off.

Here are URLs for testing a couple of terms in the path to root embedded view: http://127.0.0.1:8888/index.html?gwt.codesvr=127.0.0.1:9997&mode=embed&embed_mode=path_to_root&virtual_ontology_id=1487&concept_id=SympatheticNervousSystem http://127.0.0.1:8888/index.html?gwt.codesvr=127.0.0.1:9997&mode=embed&embed_mode=path_to_root&virtual_ontology_id=1148&concept_id=BioPortalUser

[lgrammel]

I think this issue might be related to the Flex embed we use for loading data from the NCBO REST services. It seems to appear when several calls are made in parallel. There is a Chrome/GWT dev problem that can cause it:

https://groups.google.com/forum/#!topic/google-web-toolkit/rWPxw8DQhr4

http://code.google.com/p/chromium/issues/detail?id=102048

The issue does not appear in compiled mode for me, which indicates that the Flash/JSNI/GWT Dev Code Server interaction might be causing it.

URL for compiled mode: http://127.0.0.1:8888/index.html?mode=embed&embed_mode=path_to_root&virtual_ontology_id=1487&concept_id=SympatheticNervousSystem

[drusk]

URL for bioportal equivalent of above URL http://bioportal.bioontology.org/ontologies/42651?p=terms#visualization

[drusk]

Might get fixed by #10

[everbeek]

This is still ongoing. Performing GWT compile, then running, is a workaround.

When GWT 2.5 has its official relase, we will be upgrading to it. This should improve compilation speed sufficiently that this is not really an inconvenient workaround. If that turns out well, or if GWT 2.5 fixes this without the need of compiling, then I will close this case.