Re: [Geotools-devel] deadlock CRS decode

2019-10-21 Thread Jody Garnett
There is an init method that configures referencing (and then had some trace methods that called decode to see the results). Try turning and that trace to force it to call decode as an experiment ... On Mon, Oct 21, 2019 at 7:41 AM Frank Gasdorf via GeoTools-Devel < geotools-devel@lists.sourceforg

Re: [Geotools-devel] deadlock CRS decode

2019-10-21 Thread Frank Gasdorf via GeoTools-Devel
Andrea, many thanks for your fast feedback. Going to try it with forked GeoTools first but having a look at our Application initialization-code as well. I guess its a good hint to see if CRS.decode can be run on startup Many Thanks!! -- Frank Am Mo., 21. Okt. 2019 um 15:07 Uhr schrieb Andrea Aime

Re: [Geotools-devel] deadlock CRS decode

2019-10-21 Thread Andrea Aime
On Mon, Oct 21, 2019 at 2:44 PM Frank Gasdorf via GeoTools-Devel < geotools-devel@lists.sourceforge.net> wrote: > What do you think about synchronizing CRS.decode() as well? do you expect > any performance issues or other side effects? What would you suggest to fix > this problem on master? > Wou

[Geotools-devel] deadlock CRS decode

2019-10-21 Thread Frank Gasdorf via GeoTools-Devel
Hello GeoTools Developers, recently we had some problems from within uDig with CRS.decode() and another call on CRS.getAuthorityFactory() The version we use at the moment of writing is 2.6.3 (with uDig 1.2) and I compared the code of CRS class with the current on master, where decode isn't synchr