OOPHM not connecting to Code Server

13 views
Skip to first unread message

ahawtho

unread,
Dec 1, 2009, 12:03:54 AM12/1/09
to Google Web Toolkit
When running in Development mode from the Eclipse plugin, the DevMode
console does not indicate any URL, and starting DevMode does not open
a browser. From the UsingOOPHM wiki link, I found the text:

> If you start DevMode in a browser without the plugin, you will get to the
> page allowing you to install the plugin. If you want to install it ahead
> of time, you can go directly to that missing-plugin page to install the
> plugin.

Since nothing appeared, I went to the missing-plugin page to install
the plugin, and found references to the "gwt.hosted" query param.

Our GWT pages are all served via servlets from a context URL of /
webconfig/*. We do not have a static HTML page. I tried to follow the
same pattern by navigating in FF to localhost:8888/webconfig/default?
gwt.hosted=localhost:9997 . Our application does seem to load and
function normally, but although I had run the DevMode configuration
from Eclipse's Debug menu, breakpoints don't work and I never see a
connection from the OOPHM plugin noted in the logs. I even suspended
the Code Server thread from within the DevMode JVM to see if it ever
returned from the ServerSocket.accept() (it didn't). It seems as
though the URL I'm using is bypassing the mechanism that invokes the
OOPHM plugin.

Another anomaly that I think might be related is that when creating or
editing a Run/Debug Configuration, the GWT tab on the configuration
dialog appears different when I select my GWT project (it's missing
the Browser URL field and replaces the Compiler & Shell section with a
Development Mode section, see attached images for details). I idly
wondered if it was related to our GWT bootstrap HTML pages being
generated by servlets, so I mention it here.

I found this:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b3c69a212002444b/95f9e9a0d65347f5?lnk=gst

but I verified the gwt-servlet.jar was the same in the 2.0rc2 dir and
my war/WEB-INF/lib dir .

This looks like maybe the URL field is no longer valid:

http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b688ac3e31802a6/bbc44affbff385e0

But in any case, perhaps my servlet is handling things before it gets
to yours? FWIW, I do have <load-on-startup> tags in my web.xml .

Thanks for any help,

Adam

ahawtho

unread,
Dec 1, 2009, 9:42:13 AM12/1/09
to Google Web Toolkit
Two additional pieces of information:

1. It worked in 1.7.1, but I was upgraded to a 64-bit machine running
Ubuntu 9.10, which does not include libstdc++5 anymore. I'm upgrading
to 2.0 because I can't use 1.7.1 hosted mode anymore.

2. The reference to "images" below because I was originally writing a
bug report, but I thought I'd ask to make sure I didn't have an
obvious configuration issue before reporting it, so please ignore that
part :)

Thanks to anyone who can help,

Adam
> I found this:http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
>
> but I verified the gwt-servlet.jar was the same in the 2.0rc2 dir and
> my war/WEB-INF/lib dir .
>
> This looks like maybe the URL field is no longer valid:
>
> http://groups.google.com/group/google-web-toolkit/browse_thread/threa...

Rajeev Dayal

unread,
Dec 1, 2009, 10:07:59 AM12/1/09
to google-we...@googlegroups.com
Hey Adam,

Try adding the following to the program arguments of your launch configuration:

-startupUrl webconfig/default



Rajeev


--

You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
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.



ahawtho

unread,
Dec 1, 2009, 12:43:21 PM12/1/09
to Google Web Toolkit
Thanks Rajeev,

I added that and I have good news and bad news:

The good news is that adding the cmdline arg did cause the
"Development Mode" tab in Eclipse to display a URL:
http://localhost:8080/webconfig/default?gwt.codesvr=127.0.1.1:9997,
and I was able to paste that into firefox.

The bad news is that doing so did not seem to change anything about
the execution. No breakpoints, no attempt to connect to the code
server, etc.. If you have any more ideas about this, I'd very much
appreciate it.

Side question: Does the use of the gwt.codesvr query parameter
trigger the OOPHM plugin, or is it something else?

Thanks,

Adam
> >http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
>
> > but I verified the gwt-servlet.jar was the same in the 2.0rc2 dir and
> > my war/WEB-INF/lib dir .
>
> > This looks like maybe the URL field is no longer valid:
>
> >http://groups.google.com/group/google-web-toolkit/browse_thread/threa...
>
> > But in any case, perhaps my servlet is handling things before it gets
> > to yours?  FWIW, I do have <load-on-startup> tags in my web.xml .
>
> > Thanks for any help,
>
> > Adam
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Google Web Toolkit" group.
> > 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<google-web-toolkit%2Bunsubs cr...@googlegroups.com>
> > .

ahawtho

unread,
Dec 1, 2009, 2:44:56 PM12/1/09
to Google Web Toolkit
Hi all,

This is resolved, but I'm sorry to say I can't say exactly what the
problem was. There's a few things I did that seemed as though they
may have helped:

1. We have a complex classloader structure in our servlets. We add
files to certain jar files, and because of this, there was a stray
copy of gwt-user.jar from 1.7.0 somewhere in our build process.
2. It may have been that compiling used 1.7.1 due to some old
dependencies in our custom Ant scripts, and so things were "working"
in production mode.
3. I'm not sure what caused the OOPHM plugin to connect to the Code
Server after all, my guess is that it was due to the difference
between the "gwt.codesvr" and "gwt.hosted" query parameters.

Adam

Chris Ramsdale

unread,
Dec 4, 2009, 5:01:01 PM12/4/09
to google-we...@googlegroups.com
You may have already done this, but you'll want to make sure that you update your hosted.html that you are serving up as well. In working through some other upgrade scenarios, I forgot to update this file and my app ran but wasn't hitting any of my breakpoints.

To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.

Adam Hawthorne

unread,
Dec 4, 2009, 5:24:34 PM12/4/09
to google-we...@googlegroups.com
I think the issue was not having compiled once with 2.0, which should produce the new hosted.html, correct?  Once I did that, many other things began to fail due to stray jars.  After I finally waded through that mess, things worked well.

On an unrelated note, are there any plans for a Chrome for Linux OOPHM plugin?  How different is it from the windows plugin?

Adam
--
"... that I may know Him and the power of His resurrection, and the fellowship of His sufferings, being conformed to His death, if, by any means, I may attain to the resurrection from the dead."

Chris Ramsdale

unread,
Dec 4, 2009, 5:29:23 PM12/4/09
to google-we...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages