Interesting; is it a deadlock or a timeout? If you leave it alone for 2 minuets is it able to resume? My thought is: If we manage to get the URL wrong on resume; and a mistake is made allowing the user interface to "block" on contacting the URL.
Let me know what you find out? Jody On Wed, Apr 15, 2009 at 4:49 AM, MrR08040 <[email protected]> wrote: > Hi folks, > > I'm on a CentOS 5.3 instance and I'm seeing lockups with 1.2-M3 under > jdk-6u13. Here's how to do it: > > - Remove any existing uDig workspace > - Run uDig > - Click on the Web tab at the bottom > - Click on the "jpl nasa" link and add the "Blue Marble, Global MODIS > derived image" resource > - Click Finish > - Let the map re-draw > - Click on the "dm solutions" link and the "Province" resource > - Click Finish > - Let the map re-draw > - Close uDig > - Run uDig again and witness the lock up > > I first noticed this lock up doing some prototyping with the trunk > baseline. I narrowed it down to what I believe is a deadlock > condition between two threads. Initially I thought it was something I > was doing wrong, but now that I can reproduce it with the RCP I think > there is indeed a problem in the baseline. I'll try to get some > jconsole screen shots and post them here. > > Any help on this will be greatly appreciated! > > Rob > _______________________________________________ > User-friendly Desktop Internet GIS (uDig) > http://udig.refractions.net > http://lists.refractions.net/mailman/listinfo/udig-devel > _______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
