RemoteDeathError in GWT 2.0 Developer Mode

429 views
Skip to first unread message

Dominic

unread,
Dec 21, 2009, 9:01:09 AM12/21/09
to Google Web Toolkit
I am trying to migrate a GWT 1.5.3 project to GWT 2.0.0. The
application starts fine but on most of the rpc calls, the developer
mode hangs up and a RemoteDeathError is logged. The rpc calls work in
the compiled application.

I am working with FF 3.5 on a 64bit Linux.

Anyone has an idea what the reason for the error could be?

Log:

com.google.gwt.dev.shell.BrowserChannel$RemoteDeathError: Remote
connection lost at
com.google.gwt.dev.shell.BrowserChannel.reactToMessages
(BrowserChannel.java:1683) at
com.google.gwt.dev.shell.BrowserChannelServer.processConnection
(BrowserChannelServer.java:401) at
com.google.gwt.dev.shell.BrowserChannelServer.run
(BrowserChannelServer.java:222) at java.lang.Thread.run(Thread.java:
619) Caused by: java.net.SocketException: Broken pipe 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:1341) at com.google.gwt.dev.shell.BrowserChannel
$ReturnMessage.send(BrowserChannel.java:1346) at
com.google.gwt.dev.shell.BrowserChannel.reactToMessages
(BrowserChannel.java:1671) at
com.google.gwt.dev.shell.BrowserChannelServer.processConnection
(BrowserChannelServer.java:401) at
com.google.gwt.dev.shell.BrowserChannelServer.run
(BrowserChannelServer.java:222) at java.lang.Thread.run(Thread.java:
619)

John A. Tamplin

unread,
Dec 26, 2009, 11:41:45 PM12/26/09
to Google Web Toolkit
RemoteDeathError is thrown when the connection to the browser is
closed. Are you changing the URL in your app? If you change anything
but the hash portion, it will reload the app which will drop the
devmode connection.

You can try increasing the log level with -logLevel SPAM and see what
the last call was before the connection is lost.l

Reply all
Reply to author
Forward
0 new messages