Re: [jetty-user] Double.parseDouble JVM bug

I used the GWT jetty embedded server for a while and I gave up. Memory
leak problems. Now I have an embedded Jetty server in my application
that allows me to instantly redeploy the (I mapped the F1 key within
Eclipse to hot deploy). The embedded server only have a few lines of
code.

On Wed, Feb 9, 2011 at 5:52 AM, John Tamplin <[email protected]> wrote:
> On Tue, Feb 8, 2011 at 9:56 PM, Jan Bartel <[email protected]> wrote:
>>
>> Any news from the GWT team on updating the embedded version of
>> Jetty and/or hooking into more of the jetty config files from a
>> GWT project?
>>
>> The jetty team is happy to collaborate ...
>
> Last summer when I tried to update to Jetty 7 (for WebSocket support), I ran
> into weird classloader issues with Spring/Roo/AspectJ.  Basically a class
> was getting loaded into two different classloaders, and then a cast in
> bytecode written dynamically by AspectJ was failing because the two class
> instances were not compatible.  As you can imagine, that was very difficult
> to debug, and I spent a couple of weeks on it and had to roll the change
> back to avoid disrupting GWT 2.1 being pushed.
> I haven't had time since then to look into it, and there hasn't been a big
> rush since WebSockets isn't making progress very fast, but hopefully soon it
> will and we will need to upgrade then.
> I don't know if the classloader problem is in Jetty, how we use it (we do
> some tricks to be able to reload the server to pick up changes), or perhaps
> even in Spring/Roo/AspectJ.
> If you are interested in looking into this problem, I would be happy to
> provide reproduction instructions.
> --
> John A. Tamplin
> Software Engineer (GWT), Google
>



-- 
Filipe Sousa

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email