Usually this is because some one openned a reader or writer and have
not closed it yet. It is annoying but a necessary evil. two thinks
can be done.
One - Do a search for every FeatureIterator and make sure they are all
closed. Probably search for all FeatureCollections and make sure all
iterator obtained from the collection have been closed.
Two - But a break point in the FeatureCollection features() and
iterator() methods and make sure they get closed
Jesse
On 10-Sep-08, at 11:07 AM, Aritz Dávila wrote:
Hi list,
We are developing a tool with udig sdk rc14.
I have the next problem:
I choose the tool, and start editing. I double clicked and the
feature is
added to the EditBlackboard. Until here everything goes ok, but when
I push
the commit button, commit dialog appears but never closes and uDig
gets
freezed.
After debugging, I saw it start doing the method
TransactionStateDiff.applyDiff() but when the FeatureWriter must be
closed,
it never closes it. org.geotools.data.shapefile.Lock gets locked
because the
Thread has locks and wait until it unlocks.
Could anyone tell me any possible causes of why the thread has locks?
Cheers,
Aritz Dávila
www.axios.es
_______________________________________________
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
