Re: Could not load GWT DMP Plugin

[Tony Rah]

There seems to be yet another problem with the latest Chrome plugin where it won't load in dev mode when the codesvr argument is pointing to your local ip address. Try switching the ip adress portion of the argument to either "127.0.0.1" or "localhost" in your browser. You might also have to add "-bindAddress 0.0.0.0" to you eclipse launch config.

This worked for me but I didn't dig any deeper to understand the problem more thoroughly. I also don't know how this will effect remote debugging. Perhaps someone else has better info.

On a side note, this latest plugin fixes the Chrome22/OSX issue that was plaguing everyone for the last several weeks. Unfortunately, it now introduces this new issue.

x

On Saturday, October 20, 2012 2:08:44 PM UTC-6, seas wrote:

Started getting 'Could not load GWT DMP Plugin' yesterday when I start my app from Eclipse using Chrome.  Happening on both work and home computers.  From web searches, it looks like this has happened in the past, which seemed to indicate that in those cases a new plugin was deployed that had issues.  In those cases there was no clear fix except some people has success rolling back to an earlier version of the plugin.

I've tried reinstalling the latest plugin.  Didn't see any option for downloading previous versions from the app store.  Tried restarting Chrome, Eclipse, and rebooting the machine.

Has there been a recent update to the plugin?  Where can I get the previous one to roll back to?  Is there another update coming soon that will fix this?

My home set up is:

Windows XP SP 3

Eclipse Helios Service Release 2 build ID 20110218-0911

Chrome 22.0.1229.94 m

GWT Developer Plugin 1.0.11338

My work set up is similar but with Window 7

[Rob Taft]

I just started getting the exact same issue...

[Rob Taft]

Not to mention Chrome loads an old version of my site that I can't seem to clear when I don't use the plugin...kinda left dead in the water here.

[seas]

Tony, thanks for the reply.  I didn't have much luck using different ip addresses though.  Initially, the url generated for launching in dev mode was 127.0.0.1.  I tried changing it in the Chrome address bar to local host and the machine's URL.  I also added the "-bindAddress 0.0.0.0" to the eclipse configuration.  That changed the url generated for launching dev mode to my machine's url, but still no luck.

I'll keep playing with it.

[Drew Spencer]

Same here. Glad I'm not the only one.

I'm on Windows as well, using v22 of Chrome.

Bah!

[Brian Slesinsky]

Yes, we released a new version of the plugin on Friday. For some reason, upgrading to the new plugin loses your preferences for the hostnames that Dev Mode is allowed to connect to. So you'll have to add them again. Sorry about that!

If it's not connecting and the toolkit icon on the right side of URL bar is gray instead of red, click on the gray icon to pop up the dialog to add the hostname.

An alternate way to get to the same options page:

1. visit chrome://chrome/extensions/

2. Find the entry for GWT Developer Plugin

3. Click on "Options".

- Brian

[Michael Hirsch]

Thanks, Brian.  That got me working again.

Michael

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/1Sj7A0AtI5oJ.

To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Brian Slesinsky]

Suppose the URL is: http://myhost.example.com:1234/something?gwt.codesvr=anotherhost.example.com:456

You need to add an entry to the list for "myhost.example.com" and "anotherhost.example.com" to allow this connection.

However, it's usually easier to visit the URL and click the grey icon to the right of the URL bar. If you use that dialog, it will automatically use the correct hostnames.

- Brian

On Monday, October 22, 2012 12:24:26 PM UTC-7, Cormac McLoughlin wrote:

Brian,

>> 1. visit chrome://chrome/extensions/

>> 2. Find the entry for GWT Developer Plugin

>> 3. Click on "Options".

And then what?!!  Can you please explain what we need to do in Options to get it working again?

Thanks.

[Brian Slesinsky]

Which version of Windows, and what are the symptoms?

- Brian

On Monday, October 22, 2012 1:14:41 PM UTC-7, Catherine Nantel wrote:

Thanks Brian
It doesn't work for me : Chromium Version 22.0.1216.0 (147940)
Any other idea I should try?

[Brian Slesinsky]

The Eclipse setup shouldn't matter. What error do you get in the browser when it doesn't work? Are there any messages in the Console?

Also, could you check chrome://plugins/ to make sure that there's an entry for "GWT Development-Mode Plugin"?

On Monday, October 22, 2012 4:21:30 PM UTC-7, Nomikos Zografakis wrote:

Hi Brian,

She and I are using Windows XP SP3, Eclipse 4.2 Juno, JDK 1.6 U32, Standard eclipse GWT Plugin version 2.4. The webserver and code server addresses are both 127.0.0.1 . We've set both localhost and 127.0.0.1 in the plugin options but it still doesn't work. Is there anything on the Eclipse side that needs to be set to be compatible with the Chrome extension?

Thanks

- Nomikos.

[Chris Feuz]

This workaround is also not working for me. I don't even see the toolkit icon in the statusbar. 

I'm using m2eclipse and everything worked fine out of the box until last week. 

Setup: Juno, m2eclipse, Chrome 24 dev (but also tried 22), Windows 7 

On Tuesday, October 23, 2012 1:57:23 AM UTC+2, Markus Grill wrote:

Hello Brian,

I've also the problem that the GWT DMP Plugin could not be loaded anymore

until now I've never had an entry in my preferences for the hostnames because I always used localhost as code- and webserver.

(by the way... adding localhost to the list does not work either...)

Setup: Windows7; Chrome 22.0.1229.94 m;  GWT-Plugin 1.0.11338

Markus

[Juanra Collado]

I'm with netbeans and this workaround also works for me. I either see the grey box in the direction bar

[Juanra Collado]

I'm with netbeans and this workaround also DOES NOT working for me. I either see the grey box in the direction bar

[Justin Kames]

Never had problems with GWT plugin up untill new update!

Win 7

version 22.0.1229.94 m

Reinstalled chrome/ reinstalled developer plugin multiple times keeps saying gwt dmp cant be loaded :[

[Nomikos Zografakis]

I'm getting the following stacktrace from the "Development Mode" Console at the moment the plugin fails :

08:55:04.105 [ERROR] [gablet] ManageException

com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote connection lost

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:354)

    at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:218)

    at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)

    at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)

    at com.google.gwt.core.client.impl.Impl.apply(Impl.java)

    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)

    at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)

    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)

    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)

    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:662)

Caused by: java.net.SocketException: Connection reset by peer: socket write error

    at java.net.SocketOutputStream.socketWrite0(Native Method)

    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)

    at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)

    at java.io.DataOutputStream.flush(DataOutputStream.java:106)

    at com.google.gwt.dev.shell.BrowserChannel$ReturnMessage.send(BrowserChannel.java:1310)

    at com.google.gwt.dev.shell.BrowserChannel$ReturnMessage.send(BrowserChannel.java:1315)

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:340)

    at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:218)

    at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)

    at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)

    at com.google.gwt.core.client.impl.Impl.apply(Impl.java)

    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)

    at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)

    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)

    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)

    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:662)

[Nomikos Zografakis]

Appart from Java console logs, does the plugin produce or can be made to produce logs that I can ship to you?

- Nomikos

[Drew Spencer]

Same here. This is a little disappointing, also my message above got deleted for some reason.

[Brian Slesinsky]

It looks like I linked the DLL wrong on Windows, so it requires some additional DLL's that not everyone has. We'll have a new release later today.

[seas]

Good to hear.  We'll be standing by.

[Brian Slesinsky]

A new version is now live in the Chrome store. The only difference is that the Windows version is statically linked.

I don't have a sufficient number of Windows machines available for testing, so I don't know how much this will help. However, it shouldn't make things worse.

https://chrome.google.com/webstore/detail/gwt-developer-plugin/jpjpnpmbddbjkfaccnmhnkdgjideieim

- Brian

On Tuesday, October 23, 2012 10:35:33 AM UTC-7, Brian Slesinsky wrote:

[Markus Grill]

the new version works...

Thank you

Markus

[Juanra Collado]

It's working for me the new version in:

Chrome - Versión 22.0.1229.94 m

Windows XP SP3

Thanks for your work.

[Chris Feuz]

After updating the GWT Dev Plugin to version 1.0.11349 it seems to work again on my system (Win 7/64, Chrome 22, GWT Dev Plugin 1.0.11349, Juno, m2e)

Thanks for fixing it

[Benoit Bolduc]

Version 1.0.11349 works here also.

Thanks for the fix. Really appreciated!

[Drew Spencer]

Thank you Brian! All working now.

[Leos Prikryl]

Thanks a lot. The new version works for me as well.

[Geoff Gibbs]

I have the same versions of Chrome and Windows, but it's still not working for me.

I have tried uninstalling/reinstalling but still no joy...

[Catherine Nantel]

It seems to have make things better but it still crashes.

Could it be caused by the automatic update of the plugin that overwrite your version?

[Juanra Collado]

That's true. It's loading the plugin well but is crashing in a few clicks. Hope a solution, it's so difficult programming this way.

[Nomikos Zografakis]

Hi Brian, It crashes a little later than before, but still crashed nonetheless. If there's any way I can can send you logs from the plugin, please let me know and I will send them as per your instructions.

Thanks.

- Nomikos

[Brian Slesinsky]

I have access to crash reports. Still figuring out how to use the data.

In my testing, I can start the "Showcase" sample in dev mode and it seems to work, but if I leave the browser open for a while, the plugin will eventually crash.

- Brian

[seas]

Brian,

Got the new plugin and was working fine for a bit.  Good to be testing/debugging in Chrome again.  Then this popped up: "GWT DMP Plugin has crashed.  Thank for you work on this.  Below is the stack dump.  Hope it helps.

13:52:10.421 [ERROR] [helloworld] Uncaught exception escaped

com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote connection lost

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:354)

    at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:218)

    at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)

    at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)

    at com.google.gwt.core.client.impl.Impl.apply(Impl.java)

    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)

    at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)

    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)

    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)

    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:662)

Caused by: java.net.SocketException: Connection reset

    at java.net.SocketInputStream.read(SocketInputStream.java:168)

    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)

    at java.io.BufferedInputStream.read(BufferedInputStream.java:237)

    at java.io.DataInputStream.readByte(DataInputStream.java:248)

    at com.google.gwt.dev.shell.BrowserChannel$Message.readMessageType(BrowserChannel.java:1100)

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:326)

    at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:218)

    at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:561)

    at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:269)

    at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91)

    at com.google.gwt.core.client.impl.Impl.apply(Impl.java)

    at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:213)

    at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)

    at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)

    at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172)

    at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:292)

    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:662)

[Brian Slesinsky]

I've uploaded a new version to the Chrome store that fixes a bug that could cause plugin crashes.

[Brian Slesinsky]

I'm still seeing some crash reports but I'm not sure they're the same issue. Has the situation improved at all with yesterday's release?

I just figured this out: you can report the crash to me by visiting chrome://crashes and telling me the crash id (if it's listed there).

(There is a link on that page to file a bug, but that goes to Chromium and they won't know what to do with it.)

- Brian

[Nomikos Zografakis]

It hasn't crashed with limited usage. I'll continue and report crashes using chrome://crashes

Thanks!

- Nomikos