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)
On Monday, October 22, 2012 7:44:17 PM UTC-4, Brian Slesinsky wrote:
>
> 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.
>>
>> On Monday, October 22, 2012 4:32:53 PM UTC-4, Brian Slesinsky wrote:
>>>
>>> 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?
>>>>
>>>>
>>>> Le lundi 22 octobre 2012 16:01:28 UTC-4, Brian Slesinsky a écrit :
>>>>>
>>>>> 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.
>>>>>>
>>>>>>
>>>>>> On Monday, October 22, 2012 7:09:54 PM UTC+1, Brian Slesinsky wrote:
>>>>>>>
>>>>>>> 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
>>>>>>>
>>>>>>> On Monday, October 22, 2012 5:49:24 AM UTC-7, Drew Spencer wrote:
>>>>>>>>
>>>>>>>> Same here. Glad I'm not the only one.
>>>>>>>>
>>>>>>>> I'm on Windows as well, using v22 of Chrome.
>>>>>>>>
>>>>>>>> Bah!
>>>>>>>>
>>>>>>>> On Saturday, 20 October 2012 21:08:44 UTC+1, 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
>>>>>>>>>
>>>>>>>>>
--
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/-/2n8dM_rPdT0J.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
