Re: [udig-devel] udig-1.2-M3.linux.gtk.x86 locking up

[Jody Garnett <jody.garnett@xxxxxxxxx>]

Other then deleting your udig workspace and starting again very
carefully I have no other suggestions. If you do have the ability to
run a java stack dump (connect with a debugger is one way to do this)
I would love to know what threads are blocked. Also if you can give me
step by step instructions to reproduce the problem I can try doing the
steps in my development environment. I would not expect any operating
system differences to be involved here (but I am using windows so it
would not be an exact test).

Are there any other signs? what does "top" say - is it using 100% cpu
for or it completely idle.

My volunteer time is being taken with the "climate change intergration
plugfest" (sample data and services for the foss4g conference) as such
I have not had any volunteer time for udig.

Jody

On Wed, Apr 15, 2009 at 10:30 PM, MrR08040 <MrR08040@xxxxxxxxx> wrote:
> I let it run for 10 minutes and it's still locked up.
>
> Any other suggestions?
>
> Thanks,
> Rob
>
>
> On Tue, Apr 14, 2009 at 7:06 PM, Jody Garnett <jody.garnett@xxxxxxxxx> wrote:
>> 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 <MrR08040@xxxxxxxxx> 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
>>
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
>